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

26 January 2010 at 5:27am

Hey Uncle Cheese, Can I write here about the amends I made to DOM?

facebox to use most of the screen (making it slightly more pleasing to the eye)
submit button handles better multipul uploads (instead of a hugh string for each item)

Iv attached my amends to the r343 -hope somebody finds this useful.
http://urcms.net/dataobject_manager.zip

Also can I ask what is needed to be done for many images per object? ie something like;

static $has_many = array (
'gallery' => 'Image'
);

Thanks

Avatar
UncleCheese

Forum Moderator, 4102 Posts

26 January 2010 at 5:48am

You can use a nested ImageDataObjectManager to handle multiple images per object. What do you mean by "submit button handles better multipul uploads (instead of a hugh string for each item)"?

Avatar
mattclegg

Community Member, 56 Posts

27 January 2010 at 12:54am

My submit button had the title;
"Save and add Main Image, Line Art Image1, Line Art Image2, Line Art Image3, Line Art Image4, Line Art Image5, Line Art Image6, Cadfile, Sibdata, Image Gallery 1, Image Gallery 2, Image Gallery 3, Image Gallery 4, Image Gallery 5, and Image Gallery 6"

-which used to create a huge button and scroll bars.

So using the update it will now be;
"Save and add Main Image, Line Art Image1, and Line Art Image2 And 12 other(s)."

Hopefully this makes sense

Avatar
UncleCheese

Forum Moderator, 4102 Posts

27 January 2010 at 2:40am

Lol... Definitely did not anticipate that. I'll make that update.

Avatar
bummzack

Community Member, 904 Posts

27 January 2010 at 3:40am

Hey UncleCheese

While you're updating stuff, here's another patch for you:
http://silverstripe.org/dataobjectmanager-module-forum/show/260986?start=128#post277576

Avatar
UncleCheese

Forum Moderator, 4102 Posts

27 January 2010 at 4:33am

Yup. I saw that yesterday. It's checked in, I think.

Avatar
UncleCheese

Forum Moderator, 4102 Posts

27 January 2010 at 4:42am

Actually, Banal, I'm having a hard time with this one. In my rev of DOM, I believe I have correct markup.

After the closing div for "per-page-control", there should be three closing divs, followed by $ExtraData.

<div class="per-page-control">
<% if ShowAll %>
<% else %>
$PerPageDropdown
<% end_if %>
</div>
</div>
</div>
</div>
$ExtraData
</div>

is that what you have? Also, are you seeing the issue in RelationFileDataObjectManager?

Avatar
bummzack

Community Member, 904 Posts

27 January 2010 at 6:13am

Hi UncleCheese

I got rev. 347 here.
The problem is in RelationDataObjectManager.ss at the end of the file (near: <div class="bottom-controls">) there seems to be a div missing. Which in turn messes up all following SilverStripe Tabs.

Since this is in RelationDataObjectManager, it only applies to the managers that are using this template.