I'd like to give each user (which will be set up by the admin) their own book to create and edit. The book should be viewable by anyone, but only editable by this one user. Within their own book, they should be able to add, edit and delete pages at will.
More specifically, I'm writing a site for a performing arts agent who will have several performers who she represents. Each performer would have their own book, with bio information, and then additional pages, as each performer requires (resume, headshot, etc.).
But the performer must only be able to edit their own book, not those of other performers. Everyone, including the public, needs to be able to view everything.
I've struggled and struggled to make this possible, but I'm flailing a lot, and I'm hoping someone has an idea about how this should work. It's likely very simple, but I just can't figure it out. If I give a performer access to "create book pages", they seem to be able to create book pages in anyone's book, not just their own.
Thanks from a Drupal newbie!
Comments
What you describe is my
What you describe is my greatest bugbear about the book.module - and Drupal in general - unfortunately I neither code nor make enough money to be able to do something about it. You are right, there is no way to limit what book a user can add a child page to. As a result many site developers don't use books. I have too suggestions for a workaround which I all employ to a certain extent.
* Use CCK, Views, usernode, node profile modules to create rich home sites for your users.
* Set up an Organic Group for each of your users and limit it to just one content type - this way you can even allow them to answer questions on their own forum or keep their own blog.
None of these suggestions are as straightforward as a book with proper access control would be but they mostly get the job done.
______________________
Dominik Lukes
http://www.dominiklukes.net
http://www.hermeneuticheretic.net
http://www.czechupdate.com
http://www.techwillow.com
There has been some work in this direction
See these issues:
http://drupal.org/node/81226 and http://drupal.org/node/65319
These issues seem to be on hold for now -- the most recent post in the more recent thread is about a month old.
I agree, though -- this would be some very useful functionality -- and something we will need to develop at some point for DrupalED.
Cheers,
Bill
-------
http://www.funnymonkey.com
Tools for Teachers
-------
http://www.funnymonkey.com
...
The patch/feature was to large in the shape it was in to get into 5.0 before freeze. Hopefully they will revisit the issue sooner for 6.0 and in smaller chunks.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide