[Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-13 Thread Tres Seaver
Stefan H. Holek wrote: Note that I found it to be relevant which object I want to acquire (don't ask me why, though). Because the policy checks the roles on the acquired object? As Dieter points out, 'setDefaultAccess(deny)' should only apply to subobjects which do *not* have their own roles.

Re: [Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-13 Thread Stefan H. Holek
Note that I found it to be relevant which object I want to acquire (don't ask me why, though). E.g. going back to my CMFDefault examples, I *can* acquire portal_workflow and portal_url, but I can *not* acquire portal_membership and acl_users from a denied context. Go figure. If I change the te

[Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-12 Thread Tres Seaver
Tres Seaver wrote: Dieter Maurer wrote: Tres Seaver wrote at 2004-10-9 12:04 -0400: Stefan H. Holek wrote: While testing a large-ish customer project under Zope 2.7.3 we found that when an object with setDefaultAccess('deny') is used as the context for a PythonScript, the script can no longer aqui

Re: [Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-12 Thread Tres Seaver
Dieter Maurer wrote: Tres Seaver wrote at 2004-10-9 12:04 -0400: Stefan H. Holek wrote: While testing a large-ish customer project under Zope 2.7.3 we found that when an object with setDefaultAccess('deny') is used as the context for a PythonScript, the script can no longer aquire tools from the po

Re: [Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-10 Thread Dieter Maurer
Tres Seaver wrote at 2004-10-9 12:04 -0400: >Stefan H. Holek wrote: >> While testing a large-ish customer project under Zope 2.7.3 we found that >> when an object with setDefaultAccess('deny') is used as the context for >> a PythonScript, the script can no longer aquire tools from the portal >> roo

[Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-09 Thread Tres Seaver
Stefan H. Holek wrote: On 09.10.2004, at 18:04, Tres Seaver wrote: *By definition*, anybody who has declared 'setDefaultAccess('deny') *wants* the behavior you describe: that declaration says, "unless I give you explicit permission for using a name, refuse." If Plone has classes which make such

[Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-09 Thread Stefan H. Holek
On 09.10.2004, at 18:04, Tres Seaver wrote: *By definition*, anybody who has declared 'setDefaultAccess('deny') *wants* the behavior you describe: that declaration says, "unless I give you explicit permission for using a name, refuse." If Plone has classes which make such assertions, then eithe

[Zope-dev] Re: Bad interaction between Zope 2.7.3 and CMF 1.4

2004-10-09 Thread Tres Seaver
Stefan H. Holek wrote: While testing a large-ish customer project under Zope 2.7.3 we found that when an object with setDefaultAccess('deny') is used as the context for a PythonScript, the script can no longer aquire tools from the portal root. *By definition*, anybody who has declared 'setDefaultA