I'm having problems with the access control for books and book page content.

Version: 6.9
Other related mods installed: content_access

Description:
I'm experiencing an identical problem to a user who reported here: http://drupal.org/node/350805
However, the content involved *is* a book page (even though I know the latest version of book_access makes this moot).

In a similar vein here is what I did:
- Installed book_access
- Enabled book_access in Modules
- Created a book called "News" with a number of child nodes, all using the book page content type
- Created a role called "reports team"
- Assigned a user (test account) to the "reports team" role
- Assigned permissions via: News -> Access Control tab
- Added "edit any content" and "edit own content" to "reports team"

However, that user cannot edit pre-existing content in the "News" book.
If I edit permissions via "Administer -> Permissions" then the only options enable the "reports team" role to edit/create content in *any book*, not just the "News" book.

Is there a conflict between role permissions, book_access and content_access? What should the settings be across all three of these areas for users assigned to my "reports team" role to be able to edit (but not add) content to one specific book ("News")?
Is the fact that the only created content was published by an administrator the issue here? I.e. does the 'edit any content' not apply to content created by site founder?

Comments

rmiddle’s picture

rmiddle commented

I haven't yet installed this module yet but I know there is an option to control the order in witch the access controls run. Have you tired changing that order?

Thanks
Robert

LPUK08’s picture

LPUK08 commented

Ah, no I've not tried that. I didn't realise access controls could conflict, I thought they'd just 'stack'. I've looked on Google for info on how to set priorities in access controls but no joy: I don't suppose you've a link handy to the info you'd come across?

rmiddle’s picture

rmiddle commented

LPUK08

Edit a content type go to the Tab marked Access Control on the bottom there is an Advanced Group that allows you to set the node grants priority.

Yea access control system can easily cause issues with each other. Generally the 1st to give access or prevent wins when they are stacked up. By moving this module up in the list or control access down it could make it work the way you want them to work.

Thanks
Robert

PS I am getting ready to test this module so I have no idea if that will fix the issue.

LPUK08’s picture

LPUK08 commented

Thanks for the guidance: I've tried that out but no joy unfortunately. I varied the weight from -10 to +10 but no luck in either case. It just seems as if book_access doesn't play nicely with content_access.

rmiddle’s picture

rmiddle commented

That might suck since I use content_access and was just thinking of setting up book_access.

Thanks
Robert

LPUK08’s picture

LPUK08 commented
Status: Active » Closed (fixed)

Robert, I've found the solution myself and actually it transpires that book_access is redundant. content_access will suffice on it's own for managing access to book content (on a book-by-book basis for roles).

The problem is actually this: if a book page is created using "full html" then the roles assigned to edit that page through Access Control must be able to use that input format. The default is for roles to use "filtered html" only.

Once I set up the access control via content_access, and then altered the allowed input formats for the role I'm assigning to edit book pages of a book, that role is free to go edit away.