Am 25.02.2009 um 14:18 schrieb Wichert Akkerman:
> There are many use cases for both options. One aspect is that it is
> extremely hard to not get the current behaviour. We had to hire
> to write z3c.unconfigure for us just to be able to create a system
> to prevent CMF from making changes on copies.
First of all I'm not sure if that's such a bad thing! ;-)
But the solution would probably be making this behaviour configurable
somewhere in the workflow tool.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests