Hey all,
I'm trying to set up a book within the 'Documents' area that will be accessible to Prospective Members as a guide for how to get around and who to contact regardign the different things that go on with chorus.
I've enabled the access control function so that I can show and hide specific content for different roles, but it seems that if I enable the access control for the top level, I then need to set it for all child pages independently of the top one... it doesn't flow down from there.
Is this what you have to do, or is there something I've overlooked?
Book Permissions
Mon, 01/23/2012 - 12:26
#1
Book Permissions
You have not overlooked anything... Unfortunately Groupanizer, does not follow the inherit from above rule. You have to set each new page individually. It is kind of a pain...
Carole Bergerson
Groupanizer Mistress
Alaska Sound Celebration
cbergerson@gmail.com
Which Module lets you set permissions?
Also, this should really go under feature requests. We'd like to put board business (treasurers reports and minutes) that hasn' t been approved in a protected book. but I can't really expect my users to be able to set permissions on every file they upload.
(captcha required)
Jordan Truesdell
VP - Music & Performance
Virginia Gentlemen
Roanoke, Virginia
You don't have to set permissions on every file, but you do have to set it on every page...
Tom sent me this as a possible solution http://drupal.org/project/book_access, but I have not had a chance to see if it would work for us.
Carole Bergerson
Groupanizer Mistress
Alaska Sound Celebration
cbergerson@gmail.com
I have access control set up on my documents, and have been through and set my permissions to only give prospectives access to certain docs. But they are still seeing the whole list. I want to keep it simple for them, and not have them hunting trying to find what they can get access too.
Any solutions? I did think about making a totally new book for them, but this seems the easiest route.
Works fine for music...all they see is what they have permission to see.
Philippa Gelinas
webmaster - Rhythm of the Rockies
www.rhythmoftherockies.org
I did make a new book for mine and secured it only to the Prospective Member role... which is great. Means I can have different books for different teams.
I have one for Music Team (restricted to team members), Site Admin (all my useful info, passwords etc, so that it's captured somewhere if I get hit by a bus), General (open to everyone), FAQ (open to everyone), and a couple of others.
Works great.
Antony Currington
Musical Director :: Harbour Capital Chorus
Email :: acurrington@paradise.net.nz
Wellington, New Zealand
Hi Guys,
It sounds to me like your 'Book Access' Module is turned off actually. I have created a step-by-step tutorial so you can turn it on, and then create your book access by either the book itself, or by the page. However, Carole, if you create book access at the top level, all the child pages will also automatically have the same permissions unless you change them individually (which you can do). I think your problem was more from not having the module turned on.
I hope that helps everyone!
Kari
Kari Metzger
EVP Business Development
Groupanizer
(d) 604-451-7454
kari@groupanizer.com
Interesting. I turned off the per-node access function, and enabled this, and when I log in as my Test user set to look like a Prospective Member (who should only see one book), I see all books, not just the one they should have access to.
Edit: Worked it out... for some reason the per-node didn't completely remove itself... somehow, you have to rebuild the book permissions for it to uninstall and use the book level stuff. I haven't quite worked that out, but I'm slowly getting there.
Antony Currington
Musical Director :: Harbour Capital Chorus
Email :: acurrington@paradise.net.nz
Wellington, New Zealand
Oh! Yes, you often have to rebuild permissions after this - sorry, I should have added that to the tutorial - I will now, thanks!
Kari Metzger
EVP Business Development
Groupanizer
(d) 604-451-7454
kari@groupanizer.com