Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Upgrading SilverStripe /

Ask questions about upgrading SilverStripe to the latest version.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

3.1 ConfigStaticManifest Upgrade error


Go to End


4 Posts   3104 Views

Avatar
tv

Community Member, 44 Posts

6 June 2013 at 6:08am

Has anyone received this error after upgrading and then running a dev/build?

Fatal error: Unexpected token when building static manifest: Array ( [0] => 360 [1] => => [2] => 11 ) in /Applications/MAMP/htdocs/vaultupgrade/thevault/framework/core/manifest/ConfigStaticManifest.php on line 274

Avatar
Webdoc

Community Member, 349 Posts

6 June 2013 at 6:19am

To you have in your code belongs_many_many it can cause the problem

---------------------------------------------------------------------------------------------
Arvixe Web Hosting / SilverStripe Community Liaison | Looking for quality SilverStripe Web Hosting? Look no further than Arvixe Web Hosting!

Avatar
tv

Community Member, 44 Posts

6 June 2013 at 6:35am

I have one $belongs_many_many set. After commenting it out (as well as its corresponding $many_many) I am still receiving the error.

Avatar
tv

Community Member, 44 Posts

6 June 2013 at 8:02am

Edited: 06/06/2013 8:02am

The issue was that there was a syntax error in one of my static array declarations. To track this down, I added Debug::dump($class) and Debug::dump($token) inside the while loop of ConfigStaticManifest::parseStatic ( located at line 255 ).