views:

297

answers:

2

I'm needing to set different 'create content' permissions for different user roles. This only appears to work when a particular role has not been given the "administer node" permission. However, without this permission the role does not have permission to control whether or not the node is published (which I require) or to view the content management table (Home › Administer › Content management).

For example, I want a user role to be able to create new news items and to be able to publish/unpublish them, but not create new pages (but be able to edit existing pages).

Does anyone know a way around this? Or which permissions should be set?

A: 

See the patch provided here http://drupal.org/node/214190 It looks like Drupal 7 may allow for this separation of permissions between publishing and full-blown administering, but for now you'll have to use the patch.

Dylan West
+3  A: 

Administer Nodes permission gives more access than necessary, and some modules use it as a crutch permission since it exists.

You might want to switch off this permission and implement Override Node Options module which will let users publish unpublish content. These can work in conjunction with the create/edit/delete permissions at the content type level.

Kevin
Thanks for the response, but do you know if this will allow those users to access the content management page? I'm being told that is essential.
monkeyninja
Oh, no. Without Administer Nodes, you can't get to Edit. You can, however, recreate this page with Views and put it in the administrative Content (with exposed filters too). This is what I normally do so clients don't have too much access.
Kevin
Also, you will need to make sure input filters are set correctly. Nodes that are Full HTML for example, roles will need access to that once they lose Administer Nodes.
Kevin
Thanks for the great feedback. Personally I find this standard Drupal behaviour very frustrating as you'd think that if a user can edit some content then they should be able to view a list of that content!
monkeyninja
Since discovered that the Content Management Filter module works without the administer nodes permission which gets round the content table issue.
monkeyninja

related questions