[PLIP-Advisories] [Plone] #10902: New collections (merged plip)

[Change notifications for Plone PLIPs on Trac.]

#10902: New collections (merged plip)
---------------------+------------------------------------------------------
 Reporter:  elvix    |       Owner:  jaroel
     Type:  PLIP     |      Status:  new   
 Priority:  minor    |   Milestone:  4.2   
Component:  Unknown  |    Keywords:        
---------------------+------------------------------------------------------

Comment(by alecm):

 For some advice on how migration should be handled, I recommend the
 following thread
 (http://comments.gmane.org/gmane.comp.web.zope.plone.teams.framework/3593).
 I asked Plone community members with extensive experience providing
 training and support a variety of Plone sites how the replacement of the
 collection type might impact those sites which already make use of AT
 Collections.  That thread contains their responses.  In addition to the
 on-list responses, I received one off-list response from Sam Knox (who
 does training for Groundwire clients) which provided the same conclusion
 as the rest:

 "The bottom line is that I think it's a good idea to force 4.2 sites to be
 able to only add the new Collection type. We've had sites in the past
 using both Topic and Rich Topic and that did get confusing at times."

 There seems to be broad consensus that the least confusing route would be
 to disable and re-title the old AT Collection type during migration, while
 making it clear how to re-enable adding it for those users who require AT
 Collections for some add-ons or custom templates.

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/10902#comment:32>
Plone <http://plone.org>
Plone Enterprise Content Management System