Make allowed subscription types configurable by group type

makes sense to me.

I think I had a similar feature request a while back, but mine was more along the lines of having the types of subscriptions (open, moderated, etc) configurable by the admin. Ie: If a site admin doesn't want to allow group managers to start "open" groups, they could just uncheck that selection in the OG admin and it would become unavailable on the "submit group" page, but still allow all other group types to be submitted.

there may be some other prefs which should vary by group type ... and even some prefs which are currently site-wide which should be controlled by group admin. maybe someone can chart this out and make a proposal.

keep that discussion here. we could really use a table of prefs and where they should be set ... we should be handling your SoC case better.

Still in the spirit of a group configuration panel, would it make sense to allow administrators to define which node types can be associated with different kinds of groups? One could imagine, for instance, og_type_A with nodes of type 1 and 2, and an og_type_B with node types 2 and 5. Would something like this make sense?

Has anything more ever been discussed on this feature or has it been abandoned?

What's the status of this request? I am making a site where it is very important that group content be kept private to users of each group. I would like to be able set a site-wide option (via admin account) whereby all my groups are "closed" and make it so that group managers are not able to modify that setting for their group. I am worried that a group manager might start playing around with the settings to see what they do and accidentally make their group open to the public.

Moshe, in response to your request for a proposal, here's the current og admin settings and my thoughts on what should be configurable by group type. Look forward to everyone's input.

I also think this may be a much simpler and cleaner way to address the private group issue addressed in: http://drupal.org/node/83005 since you could now create two group types with different configurations--one for private groups and one for open groups. Contrary to much discussion in that post, private and open should never be intermixed, you will totally confuse your users about the visibility of their posts. I never let my users pick visibility or audience (again users get confused). This configuation would allow me to have different settings by group type, which would be way cool.

P.S. - Great module, contrary to what Drupal says about being community plumbing, they are not without this module.

Access Control (global)

1. Enable/Disable

Group Details (per group type)

1. Groups directory control
a. new groups don’t appear
b. new groups always appear
c. group creator chooses, default in directory
d. group creator chooses, default not in directory
2. Registration form control
a. groups don’t appear
b. groups appear
c. group creator chooses, default on form
d. group creator chooses, default not on form
3. Group email notifications (could be global)
a. not subscribed default
b. subscribed default

Node Authoring Form

1. Submission guidelines (per group type)
2. Audience checkboxes (per group type)
3. Visibility of posts (per group type)
a. visible only in group
b. visible group and others
c. chosen by author, default public
d. chosen by author, default private
4. Audience required (global)
a. optional
b. required
5. Omitted content types (global)

Group Home Page (global)

1. Presentation style
2. Group home page node type

Email settings, etc. (global)

Member Pictures (global or per group type)

I've thought about this some more and it would be nice if the configuration was by group content type. Then you could have some public pages and some private pages for each group. You could allow the members to set this when they create content, but as I mentioned previously it turns into a mess if you rely on members to maintain your public/private policies.

subscribing

This functionality is now provided by the og_spaces module.

Should the ticket be closed, or is this a feature that should be integrated into og itself?

Hi mikemccaffrey, could you kindly explain how og_spaces allows this control for group creators?
I am hoping it will help with this #1034992: Allow choice for groups to have owners or be public (anyone can edit) when creating the group

Many thanks

Spaces OG basically overtakes privacy controls on a per group basis. However, this is a fairly basic feature--using Spaces OG to resolve this is like pulling out a sledgehammer when all you needed was a doctor's reflex mallet.

Routing for discussion through OG7.