Add a perm called "Edit Own Book" so that if the current user is the author of the top book page, that user can edit any page in that book... regardless of which role they've been assigned and which roles have been granted access to the book.

I have some code for this, but it's not done yet.

CommentFileSizeAuthor
#2 edit_own_book_code2.patch1.51 KBshawn dearmond
#1 edit_own_book_code.patch1.51 KBshawn dearmond

Comments

shawn dearmond’s picture

shawn dearmond commented
Status: Active » Needs review
StatusFileSize
new edit_own_book_code.patch1.51 KB

Here's a patch for this feature. I've tested it a little.

Only kinda works with nodes that are not of type: 'book' which have been added to the outline. It allows the user to modify the outline position of that node, but does not allow the user to actually edit the node. Not sure how we want to deal with those node types.

shawn dearmond’s picture

shawn dearmond commented
StatusFileSize
new edit_own_book_code2.patch1.51 KB

Here's an updated patch. It has the same functionality, it's just a little more streamlined. A little "prettier".

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented

not sure if i want to implement this feature within this module. the idea of book_access is to protect books on a per-*book* basis according to roles, not on a per-page basis according to user.

if you want finer grained control than this, you may want to look at a module such as content access.

shawn dearmond’s picture

shawn dearmond commented

In effect it is on a per-book basis. The user can access the whole book if the user is the author of the top book page.

harry slaughter’s picture

harry slaughter
Location Omaha NE USA
commented
Status: Needs review » Closed (won't fix)

Unfortunately, I have to abandon development of the D5 version of book_access. Unless someone wants to sponsor further development of the version or if proper patches are submitted, the remaining issues with D5 book_access will remain unresolved.