-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote: > Previously Charlie Clark wrote: >> Am 25.02.2009 um 16:10 schrieb Wichert Akkerman: >>> 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. >> I realise that but surely the handlers can have a default behaviour >> that can be changed depending on the configuration? > > In my opinion they should not be globally registered at all, but > available for registration in a local site manager. CMFDefault could > then do that registration for its needs.
You are in the cleft stick created by the paradox of "reusable configuration" (an oxymoron, even). The other alternative is to *not* <include/> the configuration from CMFDefault, but copy and tweak it for your own app. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [email protected] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJpXzP+gerLs4ltQ4RAnfeAKDVHNWHME5cFFuY+r0V3gtQcU7r3gCgrC3N DudQiq3r8xkvq2dbu0kwE6U= =hywa -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
