When i create a discussion post in a private space, the 'content visibility' shows 'public' eventhough the content is private (when non-members/anonymoous try to access it, access denied error is shown, as expected). The widget works correctly for the 'group' (or 'space') home page.
I added the 'group content visibility' field to 'discussion post' via og fields settings and tried all three options for the node, but the widget always shows 'public', even though each option works as expected.
(cleared cache and rebuilt permissions after each change, just to be sure :)

Comments

mpotter’s picture

mpotter commented

You should definitely not add the 'group content visibility' to the discussion post. That option is only for Group/Space content types and not for discussion posts, etc.

The bug is that the visibility widget is only looking at the settings for the Section and isn't looking at the Space itself. Will try to get this fixed, but in the meantime you'll want to revert your discussion post back to the default.

mpotter’s picture

mpotter commented
Status: Active » Fixed

OK, this should be fixed now in ec24893.

DruDoc’s picture

DruDoc commented

Hi Mr Potter, thanks for taking care of this issue. Sorry to bother you again with a small query (I am new to OA) :

You should definitely not add the 'group content visibility' to the discussion post. That option is only for Group/Space content types and not for discussion posts, etc.

If I want make any content (a single node of group content) 'private' in a 'public' space, is there any other option available other than adding 'group content visibility' field via OG fields settings.

mpotter’s picture

mpotter commented

Open Atrium is designed for you to place content within a Section (like a Discussion Section, or a Calendar Section, etc) and then set the Group/Team/Users field of the Section to control access to it. You don't set access on the node itself.

I recommend watching some of the videos linked to the openatrium project page to become familiar with the terminology and IA structure of OA2 and how privacy is handled.

Status: Fixed » Closed (fixed)

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