By chrischris on

Hello!
Is there any way I can allow a role to access certain pages, while other roles cannot?

Example:
roles anonymous, authed, group A, group B

i have written static text page that should be visible are for group B only, OR
there are some pictures I wouldlike to restrict to group A, etc.

I installed TAX, but I am no so sure this is the right module for that kind of stuff... had no luck so far.

Thanks for your help
~chrischris

⋅ Categories: Drupal 5.x

Comments

ahneill’s picture

ahneill commented

The "Simple Access" module has worked for me to restrict certain content to certain roles.... hopefully this is what you are looking for...

Art

cog.rusty’s picture

cog.rusty commented

There are several access modules for simpler or more complex setups. Currently the only ones available for Drupal 5 are:

http://drupal.org/project/taxonomy_access
http://drupal.org/project/og (organic groups)
http://drupal.org/project/forum_access

bpocanada’s picture

bpocanada commented

http://drupal.org/project/nodeaccess - this allows access by role as well as by user.

--
Roshan Shah
Drupal Designs - http://www.drupaldesigns.com A Drupal Services Company
T : 604-630-4292
--
http://www.bpocanada.com : Skype : 'bpocanada' Yahoo IM : 'bpocanada'

Our sites :
http://www.gujjuweb.com
http://www.gujaratcricket.com

xjm’s picture

xjm
she/her
Primary language English
commented

I've used several Access Control modules... one of these days I'm going to write up a book page doing a comparison of them all.

TAC is really heavyhanded and complicated, but if you're willing to have lots of redundant and otherwise unnecessary taxonomy it can do almost anything

Simple_access was too primitive for my needs. Didn't like it. Might be better for a smaller site.

Node _privacy_byrole was what I was using for awhile. It allows you to set default view, update, and delete permissions separately by content type, and then to override those for specific nodes if you like. You can also control WHO can override the default permissions. Very nice.
http://drupal.org/project/node_privacy_byrole
Caveat: disabling it adds a line to your node_access table that overrides other restrictions in the table. Always back up your database before testing access control modules.

The OG module isn't so good a choice if you don't need or want OG.

Node Access Arbitrator is apparently the wave of the future (in core for 5.0), but most access control modules for 4.7 don't use it. It doesn't do anything by itself, but it comes with a very nice module called workflow_access that lets you control permissions based on the workflow state of the node (requires the workflow module, of course). This one stands out because it has author-specific privileges and controls permissions in a logical way. It's what I'm using currently.
http://drupal.org/project/na_arbitrator
Caveat: other modules can override its access controls. E.g., CCK's access controls. It works if you disable all CCK permissions and let workflow_access take over

And as for nodeaccess, it's the new kid on the block and I haven't tested it yet, though I intend to.

==========
Feature request: HTML Source Formatting in TinyMCE

xjm’s picture

xjm
she/her
Primary language English
commented

Just noticed your post is for 5.0. Several (most?) of the modules I mention haven't been ported to 5.0 yet, so that's also a factor. :)

==========
Feature request: HTML Source Formatting in TinyMCE

xjm’s picture

xjm
she/her
Primary language English
commented

path_access comes in handy and by default doesn't interfere with other access control modules, because it operates based on path rather than specific features of nodes. I have it installed along with whatever other module I'm using.
http://drupal.org/project/path_access

==========
Feature request: HTML Source Formatting in TinyMCE

chrischris’s picture

chrischris commented

Thanks a lot!!

Yeah, unfortunately not many of these modules are 5.x, but I'll just wait a few more weeks and then decide.

Thank you!