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.

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

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

File DOM - Empty assets/ Directory (SS 2.4.2 & latest DOM)


Reply


5 Posts   1080 Views

Avatar
mi3ll

Community Member, 24 Posts

12 October 2010 at 4:22am

I am having a problem with the latest DOM downloaded from leftandmain.com, and SS 2.4.2. When I allow DOM to overwrite the assets admin, the default directory (aka assets/, the first directory which should load when you click Files & Images in the navigation bar) comes up as empty, with no options at all... and no files showing, but it has the Files and Details tab (details tab works normally).

I've had this problem with all previous installations of DOM in SS 2.4 and SS 2.3, and didn't know how to fix it (just went with a simple solution, decorated the Assets Admin with an index page that doesn't do anything but look pretty...), but it has become an issue for me (and clients) since in later versions you SS you can now upload through tinymce, and clients can upload to the assets/ folder directly but cannot view it when DOM is installed and overriding assets.

I hope there is a solution, because I really like the DOM functionality!

Avatar
mi3ll

Community Member, 24 Posts

25 October 2010 at 12:03pm

Maybe a screenshot will help:

That's how the assets folder loads, tried chmoding, an it works the same online/offline...

Avatar
Myrdhin

Community Member, 67 Posts

4 December 2010 at 3:25am

Hello,

I have the same problem. Do you find a solution ?
Thanks,

Avatar
Myrdhin

Community Member, 67 Posts

11 April 2011 at 10:13pm

No solution ? :'(

Avatar
UncleCheese

Forum Moderator, 4096 Posts

12 April 2011 at 6:48am

DOM doesn't work on the root assets folder. You can turn it off using DataObjectManager::allow_assets_override(false); in your _config.