Hello dwees,

As you can read it in the title, I'm looking to have standard books being independent one from the other as well as for role access as for page tree, unrelated to organic groups which I don't need for my project.

I tried Book Expand, installing all the complementary modules including og, but find no way to accomplish this. I'm I wrong or your module works only with og books?

Comments

dwees’s picture

dwees commented

Do you mean books which are separated by different roles, or books which are separated by different users? What are you looking to do?

I'll admit I've been focusing on the uses of this module of OG, but I did write a filter for books by role. That being said, how that filter works is that users should only be able to edit a book with which they share the same role as the original author of the book(s). It does not prevent users from submitting in more than one book, unless you somehow restrict each role to a single book (which is a simple matter of editing the function slightly).

Can you describe in more detail exactly what you are looking for?

phKU’s picture

phKU commented

Thank you dwees for your quick reply.

I'm looking to have separate books by roles. Say we have 3 books A-B-C. We would then create 3 different roles 1-2-3, each one assigned to one book A1-B2-C3. Role 1 could then edit only book A and the book A menu tree shouldn't show any page or root related to book B-C and so on for the other book/role.

A perfect solution would be to be able to duplicate the book module and thus having independent books each one with its own role access privileges. I know there is a thread about that here: http://drupal.org/node/186742, but I'm not sure if this works. I've seen another thread about separating books here: http://drupal.org/node/81226, but I'm mixed up to find workable code for the Drupal version I have (5.2).

I thought your module would do the trick better but as I wrote before it seems working only for og books...

dwees’s picture

dwees commented
Assigned: Unassigned » dwees
Category: support » bug

Sounds like a bug to me, I'll take a look at it when I get a chance.

mikaskay’s picture

mikaskay commented
Category: bug » feature

Hi dwees,

The restrict-by-Role feature works but as users get more roles the restrictions become too forgiving (e.g. if user 1 has roles A and B while user 2 has roles B and C). Would it be possible to restrict-by-Taxonomy, probably one dedicated for access rights. For example, a Vocabulary called Access with subject areas as terms where you ideally would assign only one term, such as Biology or Chemistry. So a biology major would only see biology books.

Somewhat related: with tens or hundreds of books, it becomes unwieldy to find or add content to any one book. Here the restrict-by-Taxonomy would again be helpful. It may even be linked to primary and secondary navigation. For example, let's say you click on Students (primary) and then Biology (secondary) you would only see Biology in the Book navigation block.

This is more a suggestion than a 'request' ;)

dwees’s picture

dwees commented
Status: Active » Fixed

I'm not going to be able to fix this. I've included a comment in the code so it is more obvious that this is an issue. I'm marking this "won't fix" sorry.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.