Need to specify permissions for a particular book
| Project: | node privacy byrole |
| Version: | 6.x-1.3 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
We have several different high-level book types under which we would like users to be able to create content. Currently, the only way to allow users to create new child pages is to set it within the native Drupal permissions settings. This means that creating book content is a global right, rather than a node specific right. In other words, we would like to be able to specify that some role, "Role A", can only add content under some book, "Book B". We do not want users of Role A creating a new page within Book B.
We have not been able to find a way to do so with the current configuration. Is this a feature that this module lacks or is this something that I am doing wrong?
Also, I have found that users who do not have Admin rights cannot edit the permissions of a page at all. It is our need, that if a certain user has created or edited a page, they should be able to edit the Node Privacy permissions as well. I can work around that by creating different content types for different roles, but I was wondering if there was a another way to do that.
#1
The book-specific permissions aren't possible with this module. http://drupal.org/project/forum_access does something similar to what you're asking, but for the wrong content type. Perhaps salvis is willing to write a book version.
The finest level of content permissions users can have isn't based on whether they're the author or not, just the role. That setting is in the Node privacy by role collapsed fieldset when you edit each content type as "Roles with rights to update permissions" (admin/content/node-type/page).
#2
I'd like to echo the need for this kind of feature. As it stands, there are a few hacks that encourage some pretty savage forking, but even they do not fully achieve the ability to grant node access according to a role. There exists a very real need for a better way to manage hierarchy against a process involving multiple editors.
Before the gun is pointed at me, I wish I knew how to write modules and have only written a few very basic tutorial-level modules, but I'm learning fast. Maybe I'll be lucky enough to be part of the solution if one isn't available soon.