-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Pratt wrote: > I should clarify this a bit by saying I realize that this is to identify > the default skin, however if I follow this example in my own portal and > give it a different skin name, Five stops and I have a conflict error > between this defaultSkin and defaultSkin for my own portal product. So I > am trying to find out a bit more about this to determine why this is so. > > Regards, > David > > David Pratt wrote: > >> Could someone tell me what this does in five view for CMFDefault. I am >> trying to get something basic working with my own portal product with >> five but trying to understand the zcml better. >> >> From file CMFDefault/skin/configure.zcml >> >> <browser:defaultSkin >> name="cmf" >> />
In a way, this kind of "policy" choice should not be in a redistributable product: instead, that directive should be in '$INSTANCE_HOME/etc/site.zcml'. YOu can work around the problem by using 'includeOverrides' to pull your own ZCML in, which will resolve the convlict. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFECZnf+gerLs4ltQ4RAtUxAKCjQsrzd0A81FzhjBhzePa4ElYZxgCdFcMH sx9Z59y5P69QKLLREhusqz4= =POm8 -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
