|
Author
|
Message
|
|
Luc Chase
|
Friday 08 July 2005 11:24:57 am
It seems straight forward to set policies to allow user to change own password, but what is the correct way to allow a user to change/edit their own user account (name, e-mail, password, etc.)? Adding 'selfedit' to the role policy does NOT seem to be enough.
The Web Application Service Provider
|
|
Steve P
|
Saturday 09 July 2005 2:53:23 am
I think this should be easy enough assuming your user is logged-in & permissions set correctly. /users/your_user_group/your_user ...should display a list of attributes/values & offer the chance to edit. You will probably want to create an override template. Best Steve
|
|
Luc Chase
|
Saturday 09 July 2005 5:25:44 am
Steve,
yes I agree it SHOULD be easy but it just does not seem to work. e.g.
If one takes the default editor role (which already has login, and the ability to do anything with the content class)and adds selfedit and password editing policies, it allows the user to edit the password but not get access to read or edit their details at /content/edit/<user_node_id>
the returned error is 'Your account does not have the proper privileges to access the requested page.'
The Web Application Service Provider
|
|
Jeroen Sangers
|
Friday 26 May 2006 4:10:24 am
I encountered the same problem. Anybody has a solution? Maybe the default code to generate the 'Edit Account' link in the login tool is wrong? It currently links to /content/edit/<node-id>.
|
|
Marcin Drozd
|
Friday 26 May 2006 7:59:46 am
Hi
it should be /content/edit/<user_object_id> (contentobject_id)
not /content/edit/<user_node_id>
http://ez-publish.pl
|
|
Jeroen Sangers
|
Friday 02 June 2006 10:25:33 am
Actually I wasn't talking about the code in the template (as I have no idea what template it is that takes care about the login tool) but about the produced link. So if I log on with user ID 133 (node ID 130, object ID 133), the default templates create a link in my login tool to /content/edit/133. This looks good to me, and as this user has the user/selfedit policy, I expect no problem...
|
|
Kristof Coomans
|
Saturday 03 June 2006 1:08:41 am
Hi guys The user/selfedit policy is deprecated. Use content/edit, class(user), owner(self) instead.
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Matthew Carroll
|
Monday 19 June 2006 10:36:01 am
Thanks Kristof! I just ran into a similar problem, and content edit Owner( Self ) didn't work - the reason was I had assigned that set of permissions to a sub-tree, and so the Owner( Self ) didn't apply to the user objects. Watch out for that one ;) Matthew
http://carroll.org.uk
|
