Closed (fixed)
Project:
Book Manager
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Dec 2008 at 22:44 UTC
Updated:
13 Feb 2010 at 00:20 UTC
I have the book manager module working okay, I think. But it appears that the user with only permission to use personal books have no choice to add a new node to the personal book. I would like it to behave so that the user has a choice of whether the new node is added to the personal book when created and possibly to be added afterwards. I am not sure if this is a bug or a designed feature.
When I use it with more admin book permissions, I get to have the choice of add the content to a book or not. I can select None and it is okay. I would like to give this same choice to my users.
Comments
Comment #1
mudd commentedI'm not sure if this is where you're going... When a role is given only permissions for personal books under book-manager module (and none from core book module), then the user doesn't get an outline field showing personal books when creating a new node. But I think this is default behavior for Drupal -- access conditions aren't applied to unpublished nodes.
This means that a user can't add pages until the book is published.
I find that I must publish the book. Since my site requires a workflow approval for both the books and the pages, it would be helpful if the user could add pages/nodes to unpublished books, and have the entire book hidden from public view if it's unpublished, as well as have individual pages shown or hidden based on their publication status separately.
This seems to be non-specific to Book Manager. Is there any way to accomplish this?
Comment #2
marcp commentedI am pretty sure the issue reported by rcorbett is a duplicate of #553094: "None" option missing. Book Manager forces user to create a new book anytime content is saved. which has been fixed. You should now see the option when creating content so you are not forced into creating a book.
Please re-open this if I misunderstood the issue.
Comment #3
marcp commented