It looks like Nodeacces will solve a very important problem for me, but only if it can work with Organic Groups and CCK.

I just installed the latest download from the modules page, and went through the settings to apply roles and basic access.

But, when creating content within an OG group the Grant tab is not visible either when creating content (CCK or "normal" Drupal content such as a Page) or when editing.

Does this fall under the category of "Does not play well with other access modules..."? I sure hope not. If it does, do you think Node Arbitrator will alleviate the problem? I REALLY need this to work, lol.

Thanks!

Steel Rat

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

The grant tab is not visible until the node is created. It should appear fine as long as you select the show grant tab option for each page type. I just tried it with organic groups and the grant tab shows up fine once the grant tab is enabled for the group content type, and other content types.

It will work to an extent with organic groups. However, if you are also using organic groups access control features, that will probably not work. I should say it *may* work depending on your needs. If you don't enable OG's access control, then nodeaccess will work just fine. If you want to use og and nodeaccess together, depending on how OG works, it might work ok. The problem you would run into is that drupal only requires one access control module to grant access. That means that if you want to use nodeaccess to default allow viewing of a node, but then use og to restrict it to only certain group members, that won't work. Basically you can only do addative permissions, you can't use one module to take away permissions granted by another module. It can really become quite messy however, and until drupal 5.0 is ready to go, I would recommend not using more than one access control module.

Steel Rat’s picture

Steel Rat CreditAttribution: Steel Rat commented

Thanks for the reply!

The grant tab isn't showing up after the node is created, so it must be the OG access control conflict that's occurring. I'll play around with it. There's probably no reason I can't just let Nodeaccess control access to the group. Just not sure if that will cascade to the group's objects (forums, pages, etc.).

moshe weitzman’s picture

moshe weitzman CreditAttribution: moshe weitzman commented

this simply won't work for 4.7. og is not using NA arbitrator in 4.7. og *is* using the version of NA that is in core for 5.0.

BTW, i don't like the name of this module at all. the core API is called node access so it just adds confusion to name a module node_access. people will think they need this module when they do not.

Steel Rat’s picture

Steel Rat CreditAttribution: Steel Rat commented

Thanks for jumping in, Moshe. I guess i'll have to wait for 5.0 ;)

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Active » Closed (fixed)
Rosamunda’s picture

Rosamunda CreditAttribution: Rosamunda commented
Version: 4.7.x-1.x-dev » 6.x-1.3-beta1
Status: Closed (fixed) » Active

D 5.x has passed ... and D 6.x came along, what are the options?
I´m having the same problem that you describe on #1, now on D6.

That means that if you want to use nodeaccess to default allow viewing of a node, but then use og to restrict it to only certain group members, that won't work.

Is there something that can be done?
Thanks for your help!

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Status: Active » Closed (won't fix)

clearing out old issues...

As for this, no, I don't think anything can be done. Using more than one node access module at a time is usually problematic and something I'm not going to support.