Rob Miller wrote:
the 'upgradeStep' directive as florent described in his blog entry is also a good idea, i think. i prefer the version number approach for changes that can be cleanly represented in the setup profile, but i'm sure there will be things that need to happen that the setup profile won't be able to capture effectively.
Here's an example of its use: You have a site with News documents and PressRelease documents. At some point, you decide to merge the two types into just News. Updating the profile is easy, but you'll still have to scan you database documents and modify the portal_type of the former PressReleases, and maybe adjust some attributes. That's what upgrade steps are for in CPS.
Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
