7939 Posts in 1472 Topics by 944 members
|Go to End||Next >|
26 January 2010 at 12:27am
Hello Uncle Cheese
Here's another patch for the current release of the DOM (Rev 347).
There seems to be missing a closing DIV in the RelationDataObjectManager template. When using a RelationDataObjectManager instance in the CMS, all following tabs get messed up (eg. they appear blank).
Patch is here: http://bummzack.ch/misc/RelationDataObjectManager.patch
1 February 2010 at 4:55am
I believe I'm experiencing a similar bug as banal. I'm using a recent update to SS 2.3.5 and DOM r355.
After some trial and error I got the tabs to display correctly by adding an additional div to the end of RelationDataObjectManager.ss. This makes for two div's following $ExtraData at line 110 instead of just one.
3 February 2010 at 12:29am Last edited: 3 February 2010 12:29am
the if you use SimpleHTMLEditorField in a nested data object manager it is not as big as the popup (see screen)
8 February 2010 at 1:42pm
It seems the gridview of ManyManyFileDataObjectManager doesn't display any icons (for testing purposes I also tried FileDataObjectManager, and in that case, the icons are displayed just right).
I'm on revision 359. Debugging doesn't return any errors.
9 February 2010 at 10:55pm Last edited: 10 February 2010 7:53am
When I click on an image thumbnail in the CMS to edit, I get a mess of scroll bars. Screenshot: http://drop.io/sfc6mgw/asset/picture-28-png
Wow, you're super quick with these updates. I figured I had the latest since I downloaded it not that long ago. Updated to r366, all is well.
10 February 2010 at 3:02am
Update to r366.
10 February 2010 at 1:01pm
Hi UncleCheese, and thanks for the great module!
I got an problem with DOM (r366) and latest SS2.4beta1 release. Datepickerfield didn't work properly ( pop-up appeared, but clicking the date did nothing). Firebug's diagnose was "jQuery.datepicker is undefined".
I updated the line 69 from
and it fixed the datepicker field. Not yet sure, if I messed something else up, but I hope this helps somebody with similar problems. Maybe this could be fixed in svn also?
10 February 2010 at 3:21pm
|Go to Top||Next >|