Seems like we could add a global setting for DOM to use wide mode, then, using a static property..
overridden by the instance-level:
But I don't see a reason to make changes to the JS, however, because then you're insulated from the DOM configuration, and I'd like to leave users with the highest level of control -- not stuck with what one user prefers.
This is exactly what i was looking for, i'm refering to the sortable_many_many_relation. I've been strugling with this issue for ages.
(See my post http://www.silverstripe.org/customising-the-cms/show/254721?start=0#post276300)
I downgraded to version 2.3.3. to use it and my only question now is...are you planning on making the module compatible with further versions of SS??
I just grabbed DOM Rev. 355 from SVN and apparently this bug is still open:
Since you weren't able to replicate the problem, here's a test-case for you:
The Archive contains 2 Files: DummyPage.php and ManyDummy.php. The DummyPage has a many_many relation to ManyDummy and uses ManyManyDataObjectManager to manage them.
Steps to reproduce the bug:
- copy DummyPage.php and MainDummy.php to mysite/code
- run /dev/build
- Login to the CMS and create a new DummyPage
- All tabs that come after the Tab that contains the DOM will be empty. Even the CMS Tabs like "Behavior", "ToDo" etc. will be empty. Unless you're using some browser that fixes invalid markup that is :)