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're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

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   2278 Views


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


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!


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.


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 ).