I'm using 7.x-2.0-beta1+24-dev. I just happened to notice that when content is part of a group then group members can view it even if it is unpublished.

I have a node that is part of a group. If I log in as a test user with group access rights I can see nodes that are unpublished. If I edit the node and remove it from the group then the test user can no longer view the node. If I add the node back to the group then the test user can see it again. Is this normal? I don't think a user should be able to view unpublished content just because he is a member of the group the content belongs to.

Additional settings:
In Drupal permissions I have View own unpublished content on for everybody but Anon.

CommentFileSizeAuthor
#4 1775568-og-node-unpublished-3.patch2.13 KBamitaibu
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

wimberb’s picture

Now running 7.x-2.0-beta1+41-dev (2012-Sep-13) and this issue is still present. I just wanted to bump this back up and see if anyone has a solution to prevent group members from viewing unpublished content.

spacereactor’s picture

Try using panels, http response code, Selection rules unpublished node & roles to redirect them to frontpage or custom node.

wimberb’s picture

@spacereactor Thanks for taking the time to present a possible solution. But I don't believe that would fit the bill.
First of all, the name of the unpublished content would still be visible, even though people would be prevented from actually viewing the contents.
Secondly, you shouldn't have to do something like that to prevent people from accessing unpublished content. If it is unpublished then nobody should be aware of its existence other than the admin and the author of the content. Just being a member of a Group should not give you access to unpublished content that belongs to that group.

amitaibu’s picture

Status: Active » Needs review
FileSize
2.13 KB

Lets try this. With test.

amitaibu’s picture

Status: Needs review » Fixed

Committed.

wimberb’s picture

That seems to have taken care of it. Thanks again Amitaibu for all your hard work making OG a fantastic module.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.