On Dec 9, 2009, at 16:32 , yuppie wrote: > I think it would be good to catch in .to22.check_dcmi_metadata *all* > tools that don't have a 'DCMI' attribute. > > CMF 2.0 and 2.1 did not add '_DCMI' in __init__, I just changed that > before the 2.2 beta. If the old migration code was never triggered the > tools are broken without an upgrade step.
The check has been changed. >> All scripts in CMFDefault were obsolete, those I deleted. The script in >> CMFCore is a good candidate for upgrade steps, but I am thinking the step >> should be in CMFDefault, correct? > > Yes. All migration code is now linked to the default profile of > CMFDefault. At the moment I have no idea how to make these upgrade steps > available for people who use e.g. only CMFCore. I made them all into CMFDefault upgrade steps and removed the script in CMFCore. jens
Description: S/MIME cryptographic signature
_______________________________________________ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests