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:

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

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

Help with DataObjectManager not loading

Go to End

8 Posts   1097 Views


Community Member, 25 Posts

19 October 2011 at 10:47pm

Hello I'm having some weird trouble with DataObjectManager.

This happens everytime when I wisit the SS admin for the first time after browser restart and it doesn't matter if it's with FF, Safari and Chrome.

When I log out and back in or just refresh the admin page the DataObjectManager gets loaded properly and works just fine. Until I restart the browser then SS does it again.

I think the dataobject_manager.js file isn't loaded when the problems exists but why?


Forum Moderator, 4102 Posts

20 October 2011 at 6:22am

Make sure the folder is named "dataobject_manager"

Silverstripe tips, tutorials, screencasts, and more.


Community Member, 25 Posts

20 October 2011 at 7:08am

Thank You for the attention UncleCheese but I'm afraid the folder is correctly named.


Community Member, 25 Posts

25 October 2011 at 10:51am

Any more ideas of what could cause such a thing or how to test what could be wrong? After a refresh it always starts to work.


Community Member, 349 Posts

25 October 2011 at 11:06am

Lisa mind msni aitan sind hädast välja senteet(at)


Community Member, 25 Posts

11 November 2011 at 8:12am

Edited: 11/11/2011 8:13am

Just for the record. The problem was the php end tags


at the end of my custom page type code.


Community Member, 31 Posts

12 December 2011 at 7:02pm

I was having this very problem. The formatting of the DataObjectManager fields was messed up until I refreshed with ?flush=1. It was isolated to one page which was heavily laden with extra tabs filled with DOM functionality.

The fix for me turned out to be an empty line above the opening php tag <?php on an unrelated custom page class. A tricky bugger to find, but once I removed the empty line so the php block opened on line 1 the system was happy.


Community Member, 18 Posts

17 February 2012 at 4:15pm

Thank you so much! Had the same issue! had been looking for a solution for sometime.