Closed (fixed)
Project:
node privacy byrole
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
22 Jan 2007 at 18:06 UTC
Updated:
11 Jun 2007 at 08:57 UTC
I've been using this module at one client for about a year, under previous 4.6/4.7 versions.
Can anyone suggest some good alternatives to the node privacy by role? I need certain groups of users to have access to only SOME types nodes... I've used content types to set default permissions.
Eventually I need to allow more finite control... similar to the featured in this module. my client is a business that would eventually like to allow their clients access to content created espcially for their employees and their clients.
Comments
Comment #1
brianpeat commentedI'm interested in this too. The Tax Access module is just a pain to use, and then you can use Taxonomy for its created purpose (at least not easliy). It seems like a no brainer to be able to set access to nodes by type, and even set access to each node by role from a pop-up menu in the node edit window. Makes me wonder why this wasn't built into the core.
Comment #2
mike stewart commentedFYI, looks like there's some work towards making NPBR work on drupal 5 => http://drupal.org/node/106122
Comment #3
luti commentedI agree a complete fine-tunable access permission system (per role and/or per user; to view, edit, delete, modify access permissions etc.) should absolutely find a way into the core, for any part of it (not only nodes, but also menu items, blocks, taxonomy, users etc.) - this for me is one of a key features a serious site admin needs. Otherwise, I like Drupal very much, but this really surprises me...
Well, another weirdness is so much limited weight ranges (-10 to 10 only, what would be a problem to use the whole data type range!), which is sometimes not enough for me (in particular due to a fact that user settings are fixed at weight 0, effectively limit the available weight range to a half of that only - in case you want to have this item at the top or at the bottom of menu...).
Is it really so complicated to do that?!
Comment #4
luti commentedI see not much happens with this module, so maybe it's really time to look for an alternative... :-(
Would anyone who has some experience with both modules (this one and nodeaccess, which has now an "official" 5.x-1.x-dev version, and not just some patched temporary solution...) be so kind to make a brief comparison (of features, stability, issues etc.).
Or, at least someone who has experience with nodeaccess, to answer the following:
- can I adjust the permissions for just one node (whatever the node type is...) per role, or can this be done only per node type?
- in case there are no custom settings for a node present, is this node accessible for anyone (or, can the default settings be specified for such cases), or how a system behaves in such a case?
- can settings be different for node settings privileges and for different actions (view, edit, delete) as with this module?
As with a current behavior of this module I've had to go through all pages and enter access settings, I am a bit afraid now to turn it off and try nodeaccess module (which is using its own table for privileges, as much as I see in install file, while this module, npbr, is entering the data simply into the system node_access table...).
Thank you for any feedback in advance.
Comment #5
jondoesdrupal commentedClosing this off.
Drupal 5 version is now available, and if finer permissions are required then other modules such as taxonomy access are available.