Previously Tres Seaver wrote: > -----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.
Not including CMFDefault is entirely reasonable. There are two problems though: - CMFDefault is in the Products namespace, so five will load its zcml automatically. - some of these are in CMFCore (handleDynamicTypeCopiedEvent for example, which zaps local roles from copies). Asking people to copy CMFCore configuration for a reasonably common use case is not desirable imho. Wichert. -- 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 http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
