Peter Fraterdeus wrote:
Just trying to track down an answer or a hint of a path to a solution for the
following:
Why would a custom member type generated with AGX, and following the remember
documentation on custom schema, raise an Unauthorized exception?
That is, when we set the Default Member type to our 'CustomPerson', the "join"
link raises Unauthorized, and shows a login form.
Traceback here: http://paste.plone.org/15584
VerboseSecurity isn't very telling.
yes, the unauth errors on content creation that CMF raises are not very
helpful. to really understand what's going on, you have to step into the
getSecurityManager().validate() call on link 538 of
Products.CMFCore.TypesTool. :(
We've made 'CustomPerson' addable to MemberDataContainer in portal_types.
what is the add permission on your CustomPerson type, and who has this
permission? remember sets the add permission on its member type to be "Add
portal member", which is given to Anonymous by default. this is not the case
with most content types, so maybe AGX is creating a custom add permission, or
is using "Add portal content".
if it's a custom permission, you should be able to tweak the roles on that
permission and you'll be fine. if it's not, then you'll have to figure out
how to reassign it to a different add permission, probably "Add portal member".
-r
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2007/07/1183676754917
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
