Previously Charlie Clark wrote:
> 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
> > Philipp
> > 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.
The workflow tool is not a factor at all here. The problem is that CMF
registers some event handlers that do things like clear workflow status
and local roles when you create a copy.
Wichert Akkerman <wich...@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests