-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Aspeli wrote: > > >> fixed on trunk and 1.5 branch (CMFDefault) >> >> Can you try it out with your Plone instance ? > > > Seems to work here - thanks a lot!
> > The issue now is whether we can get a new release of CMF (1.5.3 or > 1.5.2.1?) so that Plone 2.1's release schedule won't suffer. Are there > any reasons why we cannot get another CMF interim release very soon? > I can't answer this release question myself. Is Plone really using the CMFDefault default workfow definition ? if you're greping you can't find anything : [EMAIL PROTECTED] CMFPlone]$ grep -ri "DefaultWorkflowDefinition" . [EMAIL PROTECTED] CMFPlone]$ And according to this : https://svn.plone.org/svn/plone/CMFPlone/trunk/PloneWorkflow.py This is using the DCWorkflowDefinition directly. J. - -- Julien Anguenot | Nuxeo R&D (Paris, France) CPS Platform : http://www.cps-project.org Zope3 / ECM : http://www.z3lab.org mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFC28c8GhoG8MxZ/pIRAvsUAKCJwtswUd4o3RGcN4+L1PQYQGWZgwCeJLE9 bZLHntdrmMLtyhiZGgSLxls= =lAIJ -----END PGP SIGNATURE----- _______________________________________________ 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