By cattalk on
Hi,
I have a usergroup who is only supposed to see the content list under "/admin/content". To be able to a see this list they have to have the permission to administer nodes. How come this group then can also edit and delete content although "edit" and "delete" is switched off completely for every content type for this group?
Is there any other way to see the list of content in the admin?
Thx
cat
Comments
=-=
administer -> nodes give full access to node, overriding edit and delete.
If you need a content list, you should use the views.module to create that list rather then give extended permissions on nodes.
Sounds like you have given
Sounds like you have given them Administer Nodes permission ?
Look up
http://drupal.org/project/module_grants
http://drupal.org/project/revisioning
Work is being done in dev, which affects who can see what, and may benifit your needs
Good question: The administer
Good question: The administer nodes permission overrides any others, as you can see a user/role with administer nodes can edit/delete "any" node on the website.
Maybe your solution would be to create a view with the Views module to list the content.
Steve
Thanks everyone for your
Thanks everyone for your comments!
That was one thing I did not understand that when turning on "administer nodes" the "edit" and "delete" for the different content types dont have to be checked.
Of course I can put this list in a view but I was hoping this was manageable via permissions.
If I create a view in the Admin how do I grant permission for this page to only one specific group?
The problem is that this page should be available via the admin only.
thx
cat
=-=
views has permissions on it like any other content type, thus allowing you a view for a specific role without giving administer nodes permissions.
ok, thanks. I still dont get
ok, thanks.
I still dont get why you can check whether someone can edit a certain content type or not.
If "administer nodes" is not checked the user cant see the list and cannot edit anything. If its checked the user can see the list but then it does not matter what else is checked because with this list switched on the user can edit and delete everything?
Hmm...
So how would I go about if I checked "administer nodes" for a group (say "editors") and I want the editors to only look at and edit the content type "News"?
thx
cat
If you give them administer
If you give them administer nodes permission they can edit/delete "any" node on the site. Not advisable.
So if I understand.
You have content type "News".
A role "Editors".
You wish that Editors can view a list of News nodes whether published or not, and be able to edit them set them published.
Here's a rough sketch of what you might do,
Then I would set "edit any News content" for the Editors role (and create /delete if you want that).
(Views can be quite hard to figureout at first, this rough outline might assist)
Then create a view, which would display all News nodes whether or not they are published.
Filter Node type = News
Fields: all under node
Node: Delete link
Node: Edit Link
Node: Published
Node: Title (Linked to its node)
Re=order the Above
Title > Published > Edit > Delete
Basic settings:
Style: Table
Access: set to "role" then check the role (Editor) which will have access to the View.
Save:
Then add a page view click "Add display" (page)
Then under
Page settings: Path - add a path eg editors-news-list
Save
You can test your view as you build it with the preview button. Remember to save your view regularly as you build it.
Goodluck
Cool, thanks for your help
Cool, thanks for your help redpuma!
Yet another question. If this
Yet another question. If this group does not have the "administer nodes" privilege they can not decide whether or not the node is published. Any idea how to solve that?
Thanks again
cat
=-=
AFAICT, That is the only way that users can publish or promote nodes, through administer nodes permissions.
If you use views, you can create lists that show, published nodes, and unpublished nodes in separate lists. Then issue permissions on those lists which also solves your content listing that you seem to want to give users in the admin/area
Thanks for your answer! I
Thanks for your answer!
I found a solution. Its a module http://drupal.org/project/override_node_options. using this module I can allow publishing sticky etc without using administer nodes.
thx
cat
I'm a relatively new Drupal
I'm a relatively new Drupal user. I hadn't yet used Views to create custom admin pages. I wanted my editor role to be able manage and publish content, but didn't want to grant full access with "administer nodes". This worked beautifully for this purpose, and also in that I could create a much simpler interface for my non-web-savvy editors. You rule!
View using admin theme
I used redpuma's view example above, which worked great! However, I cannot get my view to use my administration theme (garland) (which is different than the site's default theme). I select Garland, save, change some other stuff with the view, save, and the theme is set back to the default...
Any ideas?