On 8/14/11 12:37 AM, David Glick wrote:
On 8/13/11 3:10 PM, Alex Clark wrote:
On 8/13/11 1:03 PM, David Glick wrote:
On 8/12/11 11:33 PM, Andreas Jung wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Raphael Ritz wrote:
On 8/12/11 6:07 PM, Andreas Jung wrote: I encountered the following
error with multiple add-ons under Plone 4.1 (working nicely with
Plone 4.0).
http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-4.0-to-4.1/updating-add-on-products-for-plone-4.1/referencemanual-all-pages
see 'updating permissions' in particular.
If you aim for backwards compatibility I'd recommend to make this
conditional on plone41 or skip the specification of the permissions
file in ZCML. Otherwise stuff will break on Plone 3.x.
This is strange - various of my own add-ons run without
modifications on Plone 4.1 - and they do of course use cmf.XXX
permissions to protect views. None of my add-ons contains
<include package="Products.CMFCore" file="permissions.zcml" />
That's why I am surprised.
It's a matter of what order packages' ZCML gets loaded. If your packages
that use CMF permissions happen to load after CMFPlone or something else
that includes CMFCore's ZCML, it will work fine. If your packages load
first, it won't unless your package also includes CMFCore's ZCML.
What determines the load order?
I'm not sure.
That might be fun to graph.
And is it "safe" to just load the
appropriate ZCML in our add-ons knowing it will get re-loaded later?
Yes. The ZCML configuration will prevent a ZCML file from being
processed. more than once.
Ah, thanks. Good to know.
----------
David Glick
Web Developer
[email protected]
206.286.1235x32
Online tools and strategies for the environmental movement.
Sign up for our newsletter: http://www.groundwire.org/email-capture
--
Alex Clark ยท http://aclark.net
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
