How to work with the book module? [#363525]

Hello there, this module is great!

I was wondering how it would be possible to handle Books from book.module using this module? My idea is to grant access to Books on a per user basis, but I noticed that giving access to the parent book does not give access to the rest of the book.

Since this module handles per user persmissions so well, I was wondering if it could be made to work with all the book pages in a book when giving the access to the parent top level page?

Any ideas of the direction we should take to do this?

thanks,

Patchak

Comments

Comment #1

irishgringo commented 3 February 2009 at 11:47

wow, i was going to ask the exact same question. My issue is that I have a book with about 30 pages of image nodes and BookPage Nodes, and I don't want to make changes to the acl or permissions to all of the pages.

the model is that I currently have a DOMAIN ACCESS system setup for 30 different sites. I want to grant this book viewable to about 8 of them... and add this capability to the rest on a random basis.

so I suppose I should also post this question in the book forum. But if anyone has an idea, I would love to hear it. I also want this to work in the OG module. But the catch is, add the book to one OG group, and all of the pages are added as well.

Comment #2

fago

German

Vienna

commented 10 February 2009 at 15:41

hm, what about using rules for that?

The only missing piece here is a rules action that loading children books. We could need rules data list support here, but one could do it also without I think. -> Do an action for loading the first children of a book page, if there is one. Then do another action that always loads the next sibling of the current book page.

Then do a rule set, that has an rule for loading the children, setting its permissions and invoking the same rule set on the children. Then add another rule that does the same for the sibling.