comments on the book access module
tihidesigns - January 16, 2008 - 19:32
| Project: | Book access |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
hello,
i like this module much, and will be using it. let me know what kind of specific testing help you need - i am running a company intranet site of about 30 users.
right off the bat i see two things that probably need correcting:
- when a private book is included as a Primary links menu item, the title displays regardless if the user has access to that book or not.
- a "create page" in book control checkbox would be usefully - i have 5 books - 3 technical manuals, 1 unfinished manual that users can edit and created content into to be folded in the previous 3 by the admin, and an admin manual. with the current system i cannot restrict user to creating new pages only to the unfinished book.
thanks and let me know how i can help.
-iova
#1
Menu items like primary links have no concept of what they link to. You can create menu items with bad links or links to things the user has no permission to access. That's not the fault of the book or book_access module.
As far as a 'create pages in this book' permissions... The book_access module implements the default grants provided by Drupal which are access, edit, delete. If a user has 'edit' access to a book *and* he has 'create book pages' access in the 'access control' settings, he will be able to create pages within that book.