I would like to have the ability to create a private group that has public content!

As stated here on #2018039: Group Content Access field is not displayed and thus cannot be used the #1964282: Streamline group privacy settings fieldset probably had the 'group content visibility' field removed from the group content edit-form. We would like to have it back.

There are general use cases, where you have a private group (group and its content hidden from non-members), but you want specific content to show up for all site visitors (non-members of the private group), like one special event which should list as an upcoming event not only for group members.
This could be achieved with the 'group content visibility' field (OG_CONTENT_ACCESS_FIELD).

As RobKoberg previously posted, this could also help with this problem:
Because of not having the ability to post group content types (those content types that have the og_group_ref field) without associating a group or to trusted contacts ( https://drupal.org/node/2057105 ). I don't want the group to show up in views or searches. I do want their content to be visible publicly in certain views and blocks. I tried to do this first with a moderated group, but there is a bug that prevents its content from showing publicly ( https://drupal.org/node/2057961 ), so I am thinking there might be a deeper issue in play here.

Comments

ceepeebee’s picture

Title: Have a private group, but public content » Have a private group, but (some) public content
Issue summary: View changes

Updated issue summary to point out, that this is a general feature request for general use cases and not only one for solving RobKoberg's problem.

WebSinPat’s picture

Yes, I miss this functionality too. (wasn't sure if I misconfigured something along the way or if it got dropped from commons).

I'd also like the reverse: in a group with publicly visible content the ability to mark some specific content as hidden/private.

Basically the ability to decide node privacy settings on a node-by-node basis, overriding the group defaults.

Anonymous’s picture

I too miss this feature.

isellakuria’s picture

This is a key feature for me as well, with the specific Commons OG assumptions we have lost granularity in the content access configuration. I've seen that the functionality has not yet been ported to version 3.12, is it foreseen to include this in forthcoming versions? Meanwhile, would it be possible to tweak the code somehow avoiding impact on other functionalities?