The module only works for the admin. Even if the another role has complete permissions, it only works for the admin. I have setup a Book KB with custom content type pages. I have installed the "node privacy byrole" and as long as I am logged in as the admin, it seems to work flawlessly. However when I am logged in as a user with priveldeges to add, edit, and delete content, it does not appear to be working. While I am creating the content I do not see the "View/edit permissions" selection. I have spent a lot of time on this trying to figure out what may be wrong, but an unable to resolve the problem.

Comments

Mac-Light’s picture

Mac-Light commented
Status: Active » Closed (fixed)

I can close this request. I found the answer.

deekayen’s picture

deekayen commented

Is there some specific advice you have that could be added to the documentation for others behind you?

ginga8’s picture

ginga8 commented
Status: Closed (fixed) » Postponed (maintainer needs more info)

Can you please tell me how you resolved this issue, I can't seem to figure it out

kenjiru’s picture

kenjiru commented

Same problem, any advice?

deekayen’s picture

deekayen commented
Status: Postponed (maintainer needs more info) » Postponed

I'm looking around to see what other access modules are doing. According to ACL, Drupal 6.3 is going to have some bugfixes to core-related to node permissions. I'll revisit this after that comes out. Feel free to remind me.

nahun’s picture

nahun commented

Yes would be very nice to know what your answer was.

Anonymous’s picture

Anonymous (not verified) commented

I just posted a comment at http://drupal.org/node/53989#comment-889255 that tells how to grant these permissions to a role.

deekayen’s picture

deekayen commented
Title: Only works for the Admin Role » Add documentation or otherwise improve workflow for granting permission to change permissions
Status: Postponed » Fixed

I added the following to the README.txt, though I'm still open to any other opinions on how this information could be more readily accessed:

Managing each content type is where you grant permissions for roles with rights to update permissions. Without doing this, you
won't see the new "View/Edit Permissions" box when editing nodes as as a non-superuser account.

The basic answer is that you need to edit each of your content types to set which roles will have rights up update permissions through Administer > Content Management > Content Types > [edit a content type and look for the Node privacy by role fieldset].

Anonymous’s picture

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

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