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

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

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

Enumerable is not defined

Go to End

16 Posts   10722 Views


Community Member, 41 Posts

2 June 2011 at 3:59am

Yes, I submitted a ticket (with a patch) when I found the solution a while ago:

I've submitted tickets before but unfortunately they always seem to be glossed over.


Forum Moderator, 5523 Posts

2 June 2011 at 1:41pm

I've submitted tickets before but unfortunately they always seem to be glossed over.

Thanks for the ticket, usually we try and review the tickets every month or so but everyone gets super busy! If you submit patches to the new github account we try and merge those much quicker. Or you can do like simon_w and bug the core devs constantly on IRC till it gets merged which works somewhat better.

I assume this is not an issue in the new 3.0 as that behavior has been removed, so the patch will likely go into branches/post 2.4 which may or may not include an actual release.


Community Member, 70 Posts

26 July 2011 at 4:04pm

Thanks for finding that, just ran into the same problem


Community Member, 15 Posts

16 March 2012 at 3:38am

Bug still exists.


Community Member, 78 Posts

9 May 2012 at 6:22pm

You saved my day.
Wondering that this bug still exists.


Community Member, 1 Post

17 September 2012 at 2:12pm

Thanks Gene!

You're a legend!


Community Member, 19 Posts

23 June 2015 at 1:56pm

I am also the beneficiary of this fix just today, many gratitude forthwith.

Voodoo Priest

Community Member, 32 Posts

28 September 2015 at 7:50am

I just want to report that the bug still exists in SS 3.0.3. It doesn't occur on local development computers or on the test environment (which lies in a subdomain of the production site) although all files, except _ss_environment.php and the .htaccess are rigorously identical.
This occurs after I have upgraded the website from 2.4.13 with the intention of catching up with the latest 3.1.x release.

Go to Top