User policy troubles...

Next topic

Author	Message
Nicklas Lundgren	Monday 10 November 2003 1:25:57 pm Hi, I must admit - the user rights part of ez is over my head. At least for the time being. I have an editor role, specifying access to content * * and user login *. Can someone please explain why this role allows adding/editing/deleting users?? Does someone have any idea about how to limit the editors access to the user-area of the admin-interface? Any help appreciated! Regards Nicklas Lundgren, Sweden
Eirik Alfstad Johansen	Tuesday 11 November 2003 2:05:39 am Hi Nicklas, Users are a class belonging to the content module. So, when you have unlimited access to this module (content * *), you will be able to edit content objects of all classes. If you were to give a role access to just the users class, you would choose the content module in step 1, select limited access, and further down the road, choose the users class. Hope that makes sense ! Sincerely, Eirik Johansen Netmaking AS http://www.netmaking.no/ Sincerely, Eirik Alfstad Johansen http://www.netmaking.no/
Nicklas Lundgren	Tuesday 11 November 2003 2:04:46 pm Alright, Eirik. Thanks for your reply, now I begin to understand this! Actually I now have managed to restrict the editors access. If I may, I have a follow-up on the same subject: I am building a multisite solution on one eZPublish installation. I am using sections to separate the different sites. By assigning the editor-role to a certain section it would be possible to restrict editors from accessing the rootnode in the contentmodule. But the admin-interface always starts in the /content/view/full/2/ which then the editor has no access to. I have tried changing this by altering RootNode in content.ini.append, to no avail. I guess I could code it manually. But it seems like a bad idea. Any suggestions appreciated, Regards, Nicklas Lundgren
Lachy Laycock	Tuesday 25 November 2003 1:39:35 am I am also interested in getting RootNode to work. [re: http://ez.no/developer/ez_publish_3/forum/developer/setting_rootnode_and_userrootnode/re_setting_rootnode_and_userrootnode ] Should a bug be submitted for this?