This is quite a handy little module, we were looking for some way to limit access to certain admin areas due to clients clicking things they shouldn't.
One of the problems we have had consistently is clients trying to add nodes of content types that do nothing without manual intervention on our part (adding links to them). But we still need for them to be able to edit pages.
Due to the fact that we cant disable 'administer nodes' or they wouldn't be able to publish anything or view the admin/content page, we just let them.
Looking at this module it just struck me, why not just add some extra permissions for content types?
Anyway, here's the patch for it we have used, it just generates a list of current content types and adds the options to the permissions page. I think just the option to be able to block access to add/page is a godsend. Works well!
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | content_type_permissions.patch | 1.17 KB | Paul Lomax |
Comments
Comment #1
Paul Lomax commentedHelps if I attach the patch
Comment #2
mrthumpz commentedThere is already fine grained control for node access in the node module. The only thing this patch does is lead to more confusion because if administer nodes is checked, then anyone that has that checked should be able to do all things with all content types. If you only want to give permission to a user to add a content type do not give them administer nodes access.
The only reason this would be helpful is because they would still have access to the admin/content page. This problem should be approached from the aspect of adding 1 permission for users to access that page, but there are a lot of details which that permission would have to take into account.
Comment #3
Docc commentedWith the 2.x version you can add your own permissions through a admin form.
So give the dev a try.
Comment #4
divbox commentedI;ve tried (using 2.x) version to add admin/content and it does not work.
Unless user has admin nodes (not part of this module) they can not see anything on admin/content, and if they do have admin nodes, they can admin content types they do not have perms to, ie edit/create/delete perms in node section are not checked for that content type.
I believe this has to do w/ what @mrthumpz said in that there are many details that go into the content permission.