Re: [Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Richard Jones
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 15 Sep 2004 01:00 pm, Chris McDonough wrote: > I'd just stick the code back in there for now and we'll see what Tres > says. This is what I've done to speed up my testing, rather than fixing all the places stuff is broken. I'll be testing for

Re: [Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Chris McDonough
On Tue, 2004-09-14 at 22:49, Richard Jones wrote: > > Yup. IOW, it looks like it used to find the first "secure_url" it could > > access and return that, even if there were other acquirable "secure_url" > > attrs before that one in the acquisition path. I'm sure the fact that > > it ignores any i

Re: [Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Richard Jones
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 15 Sep 2004 12:36 pm, Chris McDonough wrote: > > Yep, that's the situation. It appears to look for the security assertions > > for "secure_url" on A instead of B. Note that "secure_url" is an > > attribute of B. > > Yup. IOW, it looks like it

Re: [Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Chris McDonough
> Yep, that's the situation. It appears to look for the security assertions for > "secure_url" on A instead of B. Note that "secure_url" is an attribute of B. Yup. IOW, it looks like it used to find the first "secure_url" it could access and return that, even if there were other acquirable "secu

Re: [Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Richard Jones
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 15 Sep 2004 12:15 pm, Chris McDonough wrote: > On Tue, 2004-09-14 at 21:18, Richard Jones wrote: > > On the "proposals" object though, we don't have any delaration for the > > "secure_url" attribute. If I add one, or a general > > security.setD

Re: [Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Chris McDonough
On Tue, 2004-09-14 at 21:18, Richard Jones wrote: > On the "proposals" object though, we don't have any delaration for the > "secure_url" attribute. If I add one, or a general > security.setDefaultAccess("allow"), then the error goes away. This doesn't > seem correct to me. It sure doesn't sound r

[Zope-dev] 2.7 branch: attribute permission problems

2004-09-14 Thread Richard Jones
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [might dupe - sent the first copy of this from the wrong address, sorry!] I've just upgraded to use the bleeding-edge 2-7 branch (from 2.7.2, running in py 2.3.3) and I've started getting permission problems with attributes. The cause appears to be ac