Users to edit content created by others

Posted by phuile on January 23, 2007 at 8:59am

I need to have a group of users who can edit contents created by others or admin (pages, stories, events, books etc), but can't access certain other functions, such as change themes, look at or edit users profile etc. I have created a category of users called "editors" for this purpose. But even if I give them exactly the same permission under access control as authemticated users, they still can't change contents created by others, well as admin (me) who is an authemticated user, can change content created by the editors etc.

Is what I describe possible? Or do the editors all have to be "Authenticated users"? I am relunctant to do that as it opens up other things that I'd not like them to be able to see or change etc.

Thanks for any help!

Comments

You need to give them access

Posted by catch on January 23, 2007 at 11:05am

You need to give them access control for "administer nodes" - then they can change all content on the site, but are still restricted from themes/modules/blocks/users etc.

They still don't have access

Posted by phuile on January 24, 2007 at 6:34am

I tried giving them access for "administer nodes", but when I logged in as that type of user to try it out, I see the list of contents, but when I clicked edit, it says "access denied". What else do I need to give them access to? Or is there something I am doing wrong?

do authenticated users have

Posted by catch on January 24, 2007 at 2:08pm

do authenticated users have access to "view nodes"?

Let me preface this by

Posted by uNeedStuff on February 1, 2007 at 8:24am

Let me preface this by saying I'm very new to Drupal and actually found your post because I have my own question but... just to clarify.

Your Admin account has more access then authentic users. What you allow a authentic user won't effect you. If you have set up a role for the editors you need to give them the same access as an authentic user PLUS what ever else you want them to have access to. For yourself you should have the Admin account to do all the "back end" administration, and another account with less access to handle the day to day "posting" of content.

Shari

Authenticated Users and Other Roles

Posted by kbrune on February 1, 2007 at 6:34pm

Actually, any role with additional privileges does not have to duplicate what Authenticated Users are allowed to do. Anyone who is logged in automatically has all the Authenticated User permissions. Whatever permissions are assigned in other roles are added to the permissions that the user has already just for being registered and logging in (being authenticated).

It's a technical point, really. Duplicating privileges in a new role just has the same effect as the default behavior discribed above. If any role to which a user belongs has permission to perform a certain action, then the user may perform that action.

As to the "super user" account (the first account created), it's true that that account automatically has access to everything regardless of assigned roles.

Which is why it's a good idea to...

create a new "admin" or "manager" role and assign priviliges accordingly, and
create a new user account and assign it that role.

You could even take it one step further and create different roles for different admin jobs, such as "content manager", "user manager", "forum moderator", etc. and create new user accounts with that type of access. Then, if someone happens to hack your password, they don't suddenly have access to everything on your site.

Beware of INPUT TYPE

Posted by massimoi on February 11, 2007 at 6:55pm

Just a note - I got mad after it!
If you have a node (page or story or whatever) which has an input type which is non available to your users (say admin) than the user will not be able to edit the node even if he/she has the "administer content" priviledge.

Ciao,
Massimo
________________________________________________________
Massimoi :-] - http://impronta48.it - http://www.nkoni.org

________________________________________________________
Massimoi :-] - http://impronta48.it - Alba-Bra-Torino - Italy
Sviluppo Siti Web Drupal Based, CakePHP, Mapserver
http://www.corsi-drupal.it - Formazione Drupal in Langa

Many blessings on you!!

Posted by anneeasterling on March 2, 2007 at 12:46am

After hours of searching and testing and trying everything I could think of -- even imaging that categories was the issue and thinking I was going to have to redesign the entire site -- I finally came across your message. To restate (using every key word I can think of!) so that perhaps others can find this message without having to search as long as I did.

Problem: I set up a group named Administrators and gave them Administer Nodes permission, but they could not edit nodes. If users assigned to that group went to Administer >> Content >> and clicked Edit under the Operations column, they got a permissions error. The site uses Categories (category.module) with Taxonomy Access enabled (taxonomy_access.module). (Now I think that may cac_lite might work, but I don't have time to test it now.) On Administer >> Access Control >> Permissions tab, I have every item include Administer Nodes checked for the Administrators group. On the Category Permissions tab, I have every item set to Allow for the Administrators Group. BUT the Administrators still could not see the Edit tab on the nodes, which was the most important thing that I was looking for now.

Solution: Thanks to Massimo's excellent post, I checked the settings under Administer >> Input Formats and realized that I had the Filtered HTML set as the default mode and no user groups were enabled for PHP or Full HTML. Considering that all of the nodes are set to Full HTML, this was the problem. I changed the default to Full HTML, which gives all groups (including the Administrators) access to Full HTML and - voila - the Edit tab is now available and Administrators (and the Board group who we want to be editors) can administer nodes. I also added groups to the Filtered HTML and PHP so they will be accessible to groups other than User1.

This also reminded me of permission issues related to TinyMCE and IMCE, so those have also been updated so all Administrators and editors can use the WYSIWYG editor.

(There, I hope I've added enough key words to make this pop up higher in the search results! To say that I did a happy dance would be a gross understatement -- my teen daughter thought I had fallen off my rocker.)

Happy day,
Anne