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

DOM + ImageDOM breaks drag and drop reordering on DOM

Go to End

5 Posts   2085 Views

Carbon Crayon

Community Member, 598 Posts

18 November 2009 at 12:19pm

Edited: 18/11/2009 12:21pm

Hi Uncle Cheese

I appear to have found a strange bug whereby if you use an image DOM and a normal DOM on the same page, the drag and drop reordering on the normal DOM does not work. As soon as I change the ImageDOM to a FileDOM it then the normal DOMs re-ordering starts working.

When I say it doesnt work, you can check the box and as you hover over the items you get the multi directional arrow, but when you try to drag them it does nothing. I assume it must be a JS conflict of some sort?

What is strange is that I am also running the image gallery which has a normal DOM for albums and a ImageDOM for images yes seems to work fine....

Many thanks



Community Member, 150 Posts

8 December 2009 at 10:37pm

I also ran into this problem again today. Situation:

Page.php with ImageDOM
HomePage.php extends Page.php and adds DOM

SortableDataObject::add_sortable_class('Photo'); in _config.php
SortableDataObject::add_sortable_class('HomePageLink'); in _config.php

Now with this setup I was not able to reorder the DOM on the HomePage page type.

Solution (work-around):

I removed the ImageDOM in Homepage.php:


Now I was able to reorder the DOM on the HomePage page type.


Community Member, 150 Posts

27 January 2010 at 12:27am

Found solution. Drag-and-drop ONLY seems to break if ImageDOM tab is added before DOM tab. If ImageDOM is added after normal DOM everything seems to work fine:

public function getCMSFields() {
    $fields = parent::getCMSFields();

    // Add DOM tab

    // Add ImageDOM tab
    return $fields;


Forum Moderator, 4102 Posts

27 January 2010 at 2:37am

This was fixed a few revs ago. See "OMG New Stuff" thread.


Community Member, 150 Posts

29 January 2010 at 12:31am

Ok, use latest version now. Many_many thanks!