By 5dayapp on

Seeking: best solution to giving multiple roles (user levels) access to specific nodes - blocking others.

I don't mind moving all the nodes to taxonomy controls, so that's an option. I'm using node_by_role now, and it's miserable. More importantly, I am having a lot of trouble upgrading this module in CVS Drupal 4.7, though I'm sure editing the module and SQL structure a bit may do the trick (should be unnecessary).

I'm using Drupal 4.7 (from CVS), with an Apache 2.22/PHP4-4.4.4_1(BSD)/mysql-client-4.1.22/mysql-server-4.1.22

But, this aught to be a universal PHP4/5 question.

Seeking an experienced answer, given the version I'm using.

⋅ Categories: Drupal 4.7.x

Comments

quibus’s picture

quibus commented

I would like to expand your question. Since the new Drupal 5 release is coming up. I was wondering what is the way to go to controll members and give node access to certain users etc. I was browsing through the module list and didnt see anything that was usefull, although the ACL module should make an easy way to make good working node access modules.

For 4.7 I use "node privacy by role". It is pretty simple (as the name states) but allows to give different user groups access to different content.

5dayapp’s picture

5dayapp commented

I've seen this in 4.7 - node access by taxonomy.

http://drupal.org/project/taxonomy_access

This is what I'm considering. I think in real world questions, what "may" work in Drupal 5 and what "will" work in Drupal 4.7 are completely different animals, and questions.

Drupal 5 has extremely few contributed and verified Drupal 5 modules. By extremely few, I mean there's only one: Organic Groups, in the security listing. And, I didn't even see that in CVS - I got it from the website: http://drupal.org/project/og [TOTALLY OT - won't do what we need at all, no matter how cool the module.]

Someone is going to have to port node access modules, or maybe someone will explain how this is built-in with Drupal 5 (which seems to be moving toward an operating system more than a core for modular development - no negative comment intended).

NOTE: the reason I didn't use this in the beginning was because if I had a taxonomy (category) for grouping purposes, and used another term for access purposes, the one that was blocked seemed to trump the one that was used to allow access. The conflict didn't seem to have a switch or setting option to allow access if /ONE/ of the taxonomy terms was acceptable. It would be MUCH more useful if that were the case, because I don't use taxonomy just to limit access, and it can be a very powerful asset for all sorts of modules.
-
Jason A. Nunnelley
There is One Truth