By bkark on

After installing 4.5, I cannot figure out how to let users edit other user's book pages. I was able to do this in 4.4 just by enabling the "maintain books" permission for all users. What else do I need to do in 4.5 in order to make this work?

Comments

puregin’s picture

puregin commented

Hi bkark -

You need to have enabled "maintain books" for the appropriate user roles:

(administer->users->[configure]->[permissions])

You also need to have the node_privacy_byrole module either disabled or properly configured:

(administer->modules->node_privacy_byrole checked)
(administer->settings->node_privacy_byrole enabled)

If the module is enabled, you should see a grid of view and edit permissions
for the defined user roles under the edit tab for each node.
Enable edit permissions for each of the roles which should be allowed to edit the book.

Make sure that you have assigned the appropriate role to each of the users who should be editing in that role.

(administer->users->list; select user -> edit; enable desired role(s))

Hope this helps...

Regards, Djun

puregin’s picture

puregin commented

Hi bkark -

You need to have enabled "maintain books" for the appropriate user roles:

(administer->users->[configure]->[permissions])

You also need to have the node_privacy_byrole module either disabled or properly configured:

(administer->modules->node_privacy_byrole checked)
(administer->settings->node_privacy_byrole enabled)

If the module is enabled, you should see a grid of view and edit permissions
for the defined user roles under the edit tab for each node.
Enable edit permissions for each of the roles which should be allowed to edit the book.

Make sure that you have assigned the appropriate role to each of the users who should be editing in that role.

(administer->users->list; select user -> edit; enable desired role(s))

Hope this helps...

Regards, Djun

bkark’s picture

bkark commented

Thanks for the help Djun but I still can't get it to work. I did have the "maintain books" permission set for all users. I did not have the node_privacy_byrole module installed though. So I went and installed it but that didn't work either. It only seems to work for nodes other than book pages. Does that really need to be installed anyway? I would think that the "maintain books" permission is all you need since that's all that was needed in 4.4.

carlmcdade’s picture

carlmcdade commented

I htink we are sharing the same problem in that none of the permission setting in the admin form are reaching the mySQL tables. So check permissions in certain content area are ignored. I have discovered book, forums, page and content links accessibility is not available to anyone other than the first user because of this.
---------------------------
info for Drupal installation
__________________________
Carl McDade
Information Technology Consult
Team Macromedia
www.heroforhire.net

dan90@drupal.org’s picture

dan90@drupal.org commented

Coruses, also none of my book maintainers can access each others' pages. I'm wondering if it has anything to do with the fact that I did briefly have taxonomy_access and node_privacy installed. But now those modules are UNinstalled, and still the site editors cannot edit each others' pages.

(Civicspace 0.8.0.3/drupal4.5.2)

carlmcdade’s picture

carlmcdade commented

I took the 4.6 version of the book module and used it in 4.5.2. It seems to have solved the problem. You may want to look at this for your situation. I did have to add some functions to my install though.
---------------------------
Hivemindz CMSopedia
__________________________
Carl McDade
Information Technology Consult
Team Macromedia

dan90@drupal.org’s picture

dan90@drupal.org commented

... do you mind if i ask?

(i.e. you just watched yer error logs for calls to absent functions and took it from there?)

...My problem is related to the taxonomy access, apparently. Reintstalled and re-enabled it and everything works, and I now have fine-grained control beyond the dreams of avarice. But I can't work out HOW this was happening, and would love to see if I can work out why your fix worked (if, that is, it addressed the same problem)

carlmcdade’s picture

carlmcdade commented

Yes, I just follwed the trail of errors and fixed them by adding the functions needed. I don't know why it worked, I did not dig that deep into it. I did not see any patches for 4.5.2. and so followed the advice of another and tried the newer versions module.
---------------------------
Hivemindz CMSopedia
__________________________
Carl McDade
Information Technology Consult
Team Macromedia

bmargulies’s picture

bmargulies commented

I have node_privacy_byrole turned on (in both places).

There is a role called 'contributors'; my test user has it.

The role in question has 'maintain books' granted.

The node in question has access to edit the book page.

No joy ... admin log shows ...

node/51/edit denied access.

I have two nodes, one of which is fine, one suffers from this problem. gid=7 is the role I'm trying to use.

The inaccessible node ...

mysql> select * from node_access where nid=51;
+-----+-----+--------------------------+------------+--------------+--------------+
| nid | gid | realm                    | grant_view | grant_update | grant_delete |
+-----+-----+--------------------------+------------+--------------+--------------+
|  51 |   1 | node_privacy_byrole_role |          1 |            0 |            0 |
|  51 |   2 | node_privacy_byrole_role |          1 |            0 |            0 |
|  51 |   2 | node_privacy_byrole_user |          1 |            0 |            0 |
|  51 |   3 | node_privacy_byrole_role |          1 |            0 |            0 |
|  51 |   4 | node_privacy_byrole_role |          1 |            0 |            0 |
|  51 |   5 | node_privacy_byrole_role |          1 |            1 |            0 |
|  51 |   6 | node_privacy_byrole_role |          1 |            1 |            0 |
|  51 |   7 | node_privacy_byrole_role |          1 |            1 |            0 |
+-----+-----+--------------------------+------------+--------------+--------------+
8 rows in set (0.00 sec)

The node that allows edits ...

mysql> select * from node_access where nid=1;
+-----+-----+--------------------------+------------+--------------+--------------+
| nid | gid | realm                    | grant_view | grant_update | grant_delete |
+-----+-----+--------------------------+------------+--------------+--------------+
|   1 |   1 | node_privacy_byrole_role |          1 |            0 |            0 |
|   1 |   1 | node_privacy_byrole_user |          1 |            0 |            0 |
|   1 |   2 | node_privacy_byrole_role |          1 |            0 |            0 |
|   1 |   3 | node_privacy_byrole_role |          1 |            0 |            0 |
|   1 |   4 | node_privacy_byrole_role |          1 |            0 |            0 |
|   1 |   5 | node_privacy_byrole_role |          1 |            0 |            0 |
|   1 |   6 | node_privacy_byrole_role |          1 |            1 |            0 |
|   1 |   7 | node_privacy_byrole_role |          1 |            1 |            0 |
+-----+-----+--------------------------+------------+--------------+--------------+
bmargulies’s picture

bmargulies commented

If the current filter for a node is not accessible to the current user, the current user is denied edit with no comment.

jimcarter’s picture

jimcarter commented

bmargulies - you are exactly right. In my case I had "administer filters" disabled and could not see edit or delete functions unless logged in as admin. Once enabled it is working as intended. thank you

--

Jim Carter
geek with a camera.

Jahandar’s picture

Jahandar commented

3 years later, but this just gave me some trouble when I overlooked it. Much thanks!