Closed (fixed)
Project:
node privacy byrole
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Jul 2005 at 20:42 UTC
Updated:
12 Sep 2005 at 17:13 UTC
As opposed to this issue; http://drupal.org/node/27199, I can't get the view options to work. I can give roles edit permissions, but I cannot restrict viewing.
I am running 4.6.2 on a Linux box. I am also running Taxonomy access if that matters.
Comments
Comment #1
gtoddv commentedAs a followup I tested new content and previously published content and no matter whether view was checked or not made no difference.
I also made sure that the module was enabled on the settings page.
Comment #2
gtoddv commentedI think this might have something to do with the taxonomy-access module. First I might not have properly patch taxonomy.module (part of taxonomy access). I reapplied the patch and cleared the database tables:
node access
term access
term access default
If you are having trouble getting this module to work, make sure that you don't have a row in node access that has a realm of 'all'. I found that I still had that row which defeats all the more granular access settings.
I may permanently disable taxonomy.module and only use this one. If someone can tell me if they can work together (or should), I would appreciate it.
Comment #3
gtoddv commentedStill waiting to find out if the is a conflict between Taxonomy_access and node_privacy_byrole. If someone could comment on this, I would be very thankful.
gtoddv
Comment #4
JohnG-1 commentedI'm getting weird behaviour with privacy_byrole and taxonomy_access too.
I wouldn't be at all suprise if they were conflicting - though the effects are quite subtle!
I would also welcome any insights.
Comment #5
Zed Pobre commentedtaxonomy_access generates spectacularly broken behaviour. I recommend against using it. For a while, it was randomly giving edit/delete permissions to anonymous users to random nodes (with absolutely identical entries in node_access that I checked by hand).
This is almost certainly a taxonomy_access bug, not a node_privacy_byrole bug.
Comment #6
gtoddv commentedThe module is working fine now. I have also disabled the taxonomy_access module. Site has been stable for a couple of weeks now.
thanks.