[Plone-UI] Nested collection removal in Plone 4.0/4.2
Nathan Van Gheem
vangheem at gmail.com
Mon Jun 11 13:24:24 UTC 2012
I can see the use-case for nested collections and think I used them
myself in the past also but I also see how it might seem a little
silly to have collections as a container.
Perhaps the best way to accomplish this is with a behavior that allows
you to extend an existing collection? Then it's in an add-on and not
in a mysterious plone core package branch that never makes it to core.
After that I guess you'd have to group your collections in a folder.
On Mon, Jun 11, 2012 at 4:16 AM, Timo Stollenwerk <lists at zmag.de> wrote:
> I was wondering why the nested collection feature has been first removed
> from the UI in Plone 4.0 and now will be entirely removed in Plone 4.2.
> Hanno wrote that "Sub-collections have indeed been removed from the UI
> on purpose for Plone 4." here:
> Could somebody shed some light into the exact (UI) reasons for this?
> The new plone.app.collection type in Plone 4.2 will not be a folderish
> type, so it will be impossible to have nested collections in Plone 4.2
> any longer (at least without subclassing the collection class):
> The old topic type was folderish:
> Is this intentional?
> I'm asking because I wrote the dexterity-based plone.app.collection
> (http://pypi.python.org/pypi/plone.app.collection/2.0b1) for a specific
> project where we now need nested collections. Therefore I would like to
> make the collection type folderish at least for plone.app.collection 2.x.
> I don't know if plone.app.collection 2.x will ever become part of Plone
> core (this is another discussion). It would be a bit strange to first
> remove a feature and then re-add it at a later point though.
> UI mailing list
> UI at lists.plone.org
More information about the UI