I need newly created groups to have certain "stock content" already visible when the group is first created, and to have this content shared across multiple groups. I'm going to implement this as a sort of "group of groups" node access status, which would work something like this:

  • Rather than assign users to groups, groups would be assigned to the "super group".
  • Content could be assigned a "super group" audience, much as it can be assigned to a group under OG.
  • In generating a list of "home nodes" to display in a group page, the home nodes would include both content tagged for the group, and for any super groups to which that group belonged.

Most of the "under-the-hood" modifications would involved tweaking the SQL generated in og_get_home_nodes_sql. Current code will not assume sub-query support.

This issue will be used for design notes and feed back on how to create an appropriate UI for the feature.

Comments

JohnG-1’s picture

JohnG-1 commented

+1 for more audience structuring options

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (fixed)

please reopen when there is something to do. i'm cleaning the queue. no placeholders.

miromarchi’s picture

miromarchi commented
  • I see this is a very old issue. But I am still interested in a group of groups feature for organic groups.
  • In my case what I wish is to simply have the possibility to clone the add people to group feature with a similar add groups to group feature.
  • This way it would be possible to create a content type with group behavior and then assign different groups to it in order to allow members of different groups to edit the same shared content. It's a possible ipotetic way to have contents shared between multiple groups.