[Zope-CMF] Re: [Plone-developers] Bug in CMFCore.WorkflowTool?

Julien Anguenot ja at nuxeo.com
Mon Jul 18 11:14:04 EDT 2005


-----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 :

[anguenot at finlandia CMFPlone]$ grep -ri "DefaultWorkflowDefinition" .
[anguenot at finlandia 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-----


More information about the Zope-CMF mailing list