Doesn't work with Drupal 6.6 [#330520]

Sadly this module doesn't actually work with Drupal 6.6.

I installed it and see it for content pages and select which roles can view it.

Doesn't matter everyone sees the content all the time.

Comments

Comment #1

rs_hull_uk CreditAttribution: rs_hull_uk commented 10 November 2008 at 14:46

I am using this module with Drupal 6.6 and it so far I have had no problems with it.

Did you rebuild the permissions after installing it or have you done so since?

Comment #2

MGN CreditAttribution: MGN commented 10 November 2008 at 15:07

Status:

Active

» Postponed (maintainer needs more info)

The module works fine with 6.x.

Rebuilding the permissions as described by rs_hull_uk is very important. Also, you might want to explain exactly how you have set it up: what user permissions have you set for a given role, what npbr permissions for a given content type and node, etc. Do you have any other access control modules enabled that might be interfering, or is this a clean drupal 6.x install? You also might want to explain how you are testing it. The more detailed and relevant information you give, the better the response will be.

Comment #3

PerryM CreditAttribution: PerryM commented 10 November 2008 at 20:38

Thank you so much for replying.

I've messed around with the module and understand it a bit better now.

I created a Page and only authorized Silver Members to view it - and promoted it to the front page.

I assumed that when a non Silver Member saw the front page the Page would be gone - it shows. However, trying to edit or view more detail does return a "Not authorized" error.

However, a similar Page does not behave the same - it too is only for Silver Members.

But now I assume the module works and will spend more time investigating.

Thanks again and I'll report my findings later.

Comment #4

toddwoof CreditAttribution: toddwoof commented 11 November 2008 at 18:56

This might be related -- and the answer might be "so, don't do that!" but here goes:

Summary: It seems that View Own causes Node Privacy ByRole not to work.

* Drupal 6.6, Node Privacy ByRole 6.x-1.3
* View Own 6.x-1.1

(I wanted view_own to fix a set of circumstances where users can edit their own nodes, but can't view the node page, which obviously doesn't make sense; and there isn't a default permission for viewing own.)

If View Own is on, Node Privacy ByRole permissions are ignored. Example:

* I create a page and set Node Privacy ByRole permissions to allow only administrator users to view it.
* If View Own is not on, it works fine: Only users in the role "administrator" can view the page.
* If View Own is on, unauthenticated users can view the page and related menu items.
* This is true even if I turn off all the View Own permissions in the permissions page for unauthenticated users.
* Rebuilding the permissions doesn't help.
* If I turn off View Own, Node Privacy ByRole permissions work fine, immediately, without rebuilding permissions.

Comment #5

zilla CreditAttribution: zilla commented 17 November 2008 at 21:03

i think this conflict is correct, have not tried it myself -also read about a conflict between node privacy and taxonomy access control (which is documented)