Ticket #11477 (closed PLIP: wontfix)

Opened 5 years ago

Last modified 5 years ago

Can't create sub-collections

Reported by: Szerge Owned by:
Priority: major Milestone: 4.x
Component: Unknown Version:
Keywords: topics, collections Cc:

Description

I've just installed Plone 4.1.3 and everything works fine... except for the impossibility to create sub-collections (sub-topics). You can see the display with the missing "add collection" at:  http://calendar.epforum.org/Capturedcran2011020520.16.57.png/view.

In the IRC someone wrote "I think that feature was removed intentionally"...

I hope not as it is a feature I have used massively in the past, and was present in previous 4.0 releases...

Attachments

Capture d’écran 2011-02-05 à 20.16.57.png Download (42.9 KB) - added by Szerge 5 years ago.
Missing "add collection" to a collection…

Change History

Changed 5 years ago by Szerge

Missing "add collection" to a collection...

comment:1 Changed 5 years ago by hannosch

  • Status changed from new to closed
  • Resolution set to wontfix
  • Milestone changed from 4.1 to 4.x

Sub-collections have indeed been removed from the UI on purpose for Plone 4. Technically it's still possible to use them, but they aren't advertised in the default setup anymore. I think all you need to do is to add 'Topic' back to the allowed_types list of the Topic type in the portal_types tool in the ZMI to get them back.

Collections will get a major overhaul of both the UI and backend code in one of the 4.x releases (see PLIP #10902). The new implementation won't support nested collections at all anymore, so it's a good idea to stop using them at some point in your sites.

comment:2 Changed 5 years ago by Szerge

  • Type changed from Bug to PLIP

Thanks for the link to PLIP. I understand the need for change and improvement, but inheritance was a great thing. Removing inheritance will just create lots of copy and paste. After all, a simple 'directory' is also a kind of 'collection' of things that are permanently... collected... Inheritance would simply mean a sort of 'pipe command' from a collection to the outcomes of another collection. I don't want to sound like it is something trivial to do, but I imagine that there should not be a big system overhead to filter a collection already created —it would be almost like applying a collection to a directory... Does this make sense?

What I liked with Plone was precisely the ability to create a structure of Topics/Collections, mimicking a directory structure. If I want to do that without inheritance, I'll have to create a directory structure and in each of the directories, add a collection as unique item (copy the criteria from the parent) + a content panel to provide links to the children...

Anyway, Plone is great and the people who work on it even greater ;-) Thanks for your patience!

Note: See TracTickets for help on using tickets.