Re: [Zope3-Users] Where unauthorized is raised?

2006-07-21 Thread Darryl Cousins
Hi, An update on this. When I change the permission on IMemberEditForm to zope.Public or zope.View then the form is displayed. Which is why I want to find the permission checker. The principal can view other objects protected by tfws.view but not this one. If I can find where the permission is

Re: [Zope3-Users] Where unauthorized is raised?

2006-07-21 Thread Darryl Cousins
Hi, def __init__ ... self.context = self.__parent__ = context That's what I was missing in the adapter. Can I clarify this? The adapter is adapting an object (`self.context=context` in `__init__`). The field is getting an attribute from the security-proxied adapter. The permission is found on

Re: [Zope3-Users] Where unauthorized is raised?

2006-07-21 Thread Darryl Cousins
Hi Takayuki, Thanks for that. I hadn't used PostmortemDebuggingHTTP before today. Regards, Darryl Takayuki Shimizukawa wrote: Hi Darryl. 2006/7/21, Darryl Cousins [EMAIL PROTECTED]: What I need to know is where is this Unauthorized being raised to debug further (as my principal indeed

RE: [Zope3-Users] Where unauthorized is raised?

2006-07-21 Thread Roger Ineichen
Hi Darryl Hi Roger, Thanks. Is there a preferred option between using self.context = self.__parent__ = context and setting the 'locate' directive in configure. My thought is that setting __parent__ on the adapter is unecessary if locate does the job. Yes, I use most the time

RE: [Zope3-Users] Where unauthorized is raised?

2006-07-21 Thread Darryl Cousins
Cheers, Thanks for the reply. And I shall remember (he hopes). Regards, Darryl Roger Ineichen wrote: Yes, I use most the time locate=True. But right, set the parent explicit is also Ok. I don't thnk there is a preferred way. just remember, the missing location on a adapters is most the