This request is similar to http://drupal.org/node/24856
This feature was never fully realized, and I would like to begin again the process for creating this feature as it is critical for the type of website we are building.
As it stands now:
By using the node_privacy_byrole module, we can restrict Read and/or Edit access by user role. This is almost perfect in that when we disable Read permissions for a role, that book is not visible on the Parent dropdown when creating a new book page. However, that book is also not visible to be read and reviewed via the Userreview module.
By following the recommendations at http://drupal.org/node/24856, we can make it so that even though a book is selected as the Parent, all submissions get put into a moderation queue where they won't actually be added to the book unless approved. Unfortunately, all a writer sees is that their book _appears_ to be appendable by anyone. Unfortunately, for the resource we are trying to provide, that just won't do.
What we require:
- A modification to the Book module that will allow _only_ creators of a book to make changes to their book. This includes adding pages, editing pages, revisions, etc.
- A user other than the creator of a book may review that book via the Userreview module, but a user other than the creator of a book will not be able to see that book in the Parent dropdown list when creating a new book page.
This feature may already be implemented, either through some configuration of the modules mentioned above, or through another module not yet installed on our site. If any such avenues exist, we are unaware of them and would appreciate any insight you could offer.
If there are no existing modules that can handle the functionality described above, what is the likelihood of something like this being implemented, and what kind of timeline would we be looking at?
Looking forward to your comments,
--
Literary Alchemy Development Team
Comments
Comment #1
tidalx3 commentedI am looking for the same thing. Initially, I thought one could choose between making the book personal(personally add and edit only) or making it public/collaborative, but I found out this was not the case.
Perhaps the profile page should also list all the user's personal books?
Comment #2
Paul Natsuo Kishimoto commentedFeature requests should be against the development version - updating to 4.7.x-dev.
Comment #3
Zen commentedMoving.
Comment #4
ChrisKennedy commentedThis is not critical. http://drupal.org/node/45111
Comment #5
pwolanin commentedAlmost got something like this in 6.x, but there is more meta data for each book in 6.x so that with some creativity you could implement this in a contrib module.
Comment #6
jody lynnThis feature can be done as a contrib module. It doesn't seem compelling as a core feature.