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 forum.silverstripe.org 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.

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

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

OMG NEW STUFF!


Go to End


28 Posts   3928 Views

Avatar
mattclegg

Community Member, 56 Posts

28 January 2010 at 5:24am

Edited: 28/01/2010 5:25am

Re: hasNested

Line 43 (dataobject_manager.js) should be
w = $(this).attr('rel') == 'duplicate' ? (($(window).width() / 6)*2) : (($(window).width() / 3)*2);

making a big box -regardless of if nested & creating a bigger box for duplicated windows (I think this might need changing somewhere else also)

Avatar
UncleCheese

Forum Moderator, 4102 Posts

28 January 2010 at 5:41am

You can use setWideMode() for that, no?

Avatar
mattclegg

Community Member, 56 Posts

28 January 2010 at 6:15am

Edited: 28/01/2010 6:15am

but I always want a big box -unless its in a box

Avatar
UncleCheese

Forum Moderator, 4102 Posts

28 January 2010 at 6:36am

Seems like we could add a global setting for DOM to use wide mode, then, using a static property..

DataObjectManager::set_wide_mode(true);

overridden by the instance-level:

$myDOM->setWideMode(false);

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.

Avatar
mattclegg

Community Member, 56 Posts

28 January 2010 at 6:52am

yeah, sounds good. Id only changed it from a static value in the first place to give the user the most their screen could handle..

Avatar
Stefdv

Community Member, 110 Posts

28 January 2010 at 7:13am

UncleCheese, you nailed it.

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

Well anyway thank you so much.

Avatar
UncleCheese

Forum Moderator, 4102 Posts

28 January 2010 at 7:32am

It will be good to go for the 2.4 release. There's a link to a ticket somewhere in this thread. It got resolved yesterday.

Avatar
bummzack

Community Member, 904 Posts

1 February 2010 at 9:16pm

Hi UncleCheese

I just grabbed DOM Rev. 355 from SVN and apparently this bug is still open:
http://silverstripe.org/dataobjectmanager-module-forum/show/260986?start=128#post277576

Since you weren't able to replicate the problem, here's a test-case for you:
http://bummzack.ch/misc/DOM-Testcase.zip

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 :)