I've been trying to limit visibility options via workflow access on a content type that is added into organic groups within the site. I tried to make visibility available to one role but every role can still view it. I know the workflow access module documentation says that:
"if a user has access through Organic Groups, he/she will be able to view a node, even if the workflow
permissions would not otherwise allow it."

I enabled og_actions to add the "remove the node from all groups" action where the state change occurs to take it out of OG and allow workflow access to affect it, but users within those groups can still view the post (even though it's removed from the group and should not be visible because of workflow access limits).

Am i going about this the right way/making it way too complicated? Thanks for any help you can give.

Comments

mblazke’s picture

mblazke commented

I have similar request on my site, although I do not need visibility per role for OG'ed nodes as you stated.

AFAK there are two important Boolean attributes:
node.publish - if false, only the author of the node can see the node
node.OG_public - if false, onle the OG members can see the node (of course node.publish has to be true too)

That's why I (and everybody else too:-) ) had to precise tune the actions related to state changes (eg. Make node publicly visible or Unpublish node) in the workflow settings.

At the same time - check your checkboxes on yoursite/admin/build/workflow/edit/workflow# just below the Access control.
There are three columns (can see/can edit/can delete) there per each workflow state per each user-role.
But - as you already quoted - those checkboxes come into game for non-OG nodes (and non-other-way-accessible nodes), because the access rights are additive only, not substractive.

Michal

Bastlynn’s picture

Bastlynn commented
Status: Active » Closed (won't fix)

Hi,

With the release of Drupal 7, Drupal 5 is no longer receiving security updates, reviews, or development from many contributed modules. Since 5 is now considered a depreciated version, you really should seriously look into upgrading to Drupal 6 or 7. The newer versions of Drupal work better, have more support, and will be safer (literally! security patches!) for your website. We are currently working on a new release for Workflow to Drupal 7. In light of that, further support for Drupal 5 issues is infeasible at the moment. Please consider upgrading to Drupal 6 or 7 in the near future - you'll be glad you did.

- Bastlynn