Restrict Content Types by OG Type

Let me see if I understand correctly...

You have defined several content types and selected them as group home pages (i.e. those that can be chosen from to start a new group). You would like for each of these to have a predefined set of ALLOWED content types. In the admin section, you might see something like 'Site-wide', 'Default', 'Type A', 'Type B', 'Type C', followed by individual groups.

Is that what you're getting at?

That's interesting indeed. I think that this idea IS in keeping with the aims of this project. I'm not sure, however, whether I would add this to the module itself, or create an add-on module. I lean toward directly changing this module for this since it will have to touch so many functions. This is not a trivial request. It will take a lot of work. I wish more people were using this module (maybe they are and I just don't know) so that I could be sure I've already got a strong base module to start from.

In any case, I probably won't have time until the end of summer to add something this big. Are you able to program yourself? I'm open to patches at any time. I'm going to mark this issue as 'postponed' because I definitely want to do this at some point.

Great idea.

subscribe

This would be a very useful feature. I came here to suggest it and am pleased to see that it has already been suggested and that the suggestion was well received by the project maintainer. Ezra, have you made any progress with this?

I agree. This would be extremely useful.

Any advance in this field? it would be usefull for me as well

Definitely need this too.

Any progress on this issue?

I'm particularly keen to see this implemented as I'm using the new Domain module and the (quirky?) node access rules in og_user_roles don't work well with Domain.

I'm looking to use this module to restrict the creation of content within the groups to only the Group Owner and the Group admins. This leaves group subscribers/non-subscribers only able to comment on group postings, and not create content.

Does anyone have any idea how much effort this would take to code? Our charity might be able to sponsor some development if the cost was low enough.

I wish I had time right now to work on this but I don't. As for how much programming, #1 addresses that. There are a lot of functions that would have to be changed if only a little. I suppose it might be mostly keeping track of what needs changing and then doing it right. Storage of each group type would be done the same as the site-wide and default "groups", so really, examples of what to do are there to some extent.

One thing to note is that the "default" group has a fake group ID of 0 since it will never be used as a real group ID. Likewise, the "site-wide" group has an ID of -1 for the same reason. Any additional fake groups would need to have smaller negative numbers assigned to them.

If anyone starts this and has questions about the code, just ask.

a workaround here that might reduce the effort to pull this off would be to simply change the group details menu. this is sort of how we are pulling off this functionality right now. we create our own group details menu blocks for each different og group node type to allow creation of the proper associated group post content types and then disable the out of the box group details menu.

This is precisely how we have achieved this on our site, for two different types of group. However, this does rely on security by obscurity on the url for the node add.

My primary reason to use this module is this specific feature.

This feature is exactly what i need too, any progress?
+1 subscribe

Related to this thread, please see my patch to og here:
#433884: Restrict posting to group admins - read only groups

I'm among ones who need the feature! This ability enables drupal sites to handle more complex content structure. Hope to see a patch or addition to og.

This feature would be a sweet addition. This module looks like it would perfectly place in the missing puzzle pieces of organic groups.

It's July now, is there any thoughts of this feature moving forward?

I would really like to see this as well.

see also:
#583422: adding a group content type button to specify the groupposts for that contenttype?

(I've marked that issue as a duplicate of this one.)

As the starter of http://drupal.org/node/583422 i'm very interested in this feature as well, (would make OG a lot more complete)

and curious about any new developments......

Subscribing +1

As far as i'm concerned i think we are on one line.

I'm looking for a feature to be able to create following scenery:

Groupcontenttype 1

Postable by groupadmin of GroupContentType 1
Grouppost contenttype: article
Grouppost contenttype: message

Postable by groupmember of GCT 1
grouppost contenttype: message

Groupcontenttype 2

Postable by groupadmin GCT 2
Grouppost contenttype: article
Grouppost contenttype: poll
Grouppost contenttype: message

Postable by groupmember GCT 2
grouppost contenttype: message
grouppost contenttype: poll

Yes, another restatement, because #23 focused on permissions:

Associate content types with a specific group content type. Thus, my groups of type "Project" can all have the "Roadmap" content type, but not my "Workgroup" groups.

#23 and #24 is exactly what we've been looking for in og since we first started using it 2 years ago.

This feature would be a huge help for me as well. We have 50+ groups of one type and 10-15 of another, and all should be configured the same (certain content types can only be posted to group type 1, other content types can only be posted to group type 2). A big thumbs up for this enhancement.

I've got a module underway to do this with a tentative due date for 1st week of March. It will be an expansion/modification of og by audience module.

subscribing

Subscribing

There is a module that does this called Audience By Type. However it does not work and is not maintained. You can still install it and see how it's supposed to work, I think it's the right approach but let me emphasize that it is infested with bugs and will cause great misery if you try to use it.

This was postponed two years ago and it's important, so I'm changing it to Active. Hope nobody minds.

I have attached a module that serves this purpose. Please review and provide feedback.

Seems to work perfectly, you're a lifesaver. My only suggestion would be to move it from "site configuration" to "organic groups" in the admin menu

subscribing

not working with og 2.x-dev release. can you please re-roll the module. group details block still shows disallowed types.

subscribing, looking for the same, to limit content types to specific group types.

@ethangj The module in #32 works.

However, if user is member of more than one group the content create form shows users the audience check boxes which to begin with are all empty along with the message "This post will be Public" rather than the default og message "Show this post in these groups". The default message is applicable to to a wider range of cases, including when groups are configured to require an audience is selected. The message with this module is not suitable with such a case.

I've just explored using both the og_content_type_admin and og_separate_groups modules.

I like the og_separate_groups module approach much better.

The og_content_type_admin is very complex to configure and has to be done for each group.

The og_separate_groups requires ctools and strongarm modules.

It allows content types to be assigned by group type which is much better for my uses.

The only drawbacks with og_separate_groups are:

1. As mentioned in comment #37, under the audience boxes on the content create form there is an extra line that declares the post will be public or private, but this may not be reflective of the site actions when configured to make an audience mandatory.

2. The site og-admins also no longer see the check box to make a post public on the content create form. As a work around privileged users can use VBO to make posts public.

Is there a good way to change both of these, to essential restore the part following the audience check boxes back to the og default, remove the extra message and allow og admins to see the public check box?

Thanks.

Here is some more feedback on the proposed options to restrict content type by og group type:

1. Using the og_content_type_admin

It still looks to me like this module involves a complex configuration. I have not actually tested this yet and may be misunderstanding the complexity from the readme file.

2. Using the og_separate_groups module.

This is quite simple to configure.

However, there is a critical bug. When this module is enabled, creating or editing content no longer displays the public check box and if a privileged user with og admin permissions creates content the post defaults to being public even if it is a post in a private group.

og_separate_groups doesnt seem to work, I still see group post for a group I dont want it in...

@ethangj

Regarding the og_separate_groups module in #32, can you help me understand what part of the code is causing the issue described in #39 item 2 ?

On the create content form, without og_separate_groups, immediately below the audience options privileged users see a public checkbox (screen capture attached).

When the og_separate_groups module is enabled it is modifying the create content form and the public checkbox is no longer visible and the post is forced to public.

Can you help me understand what part of the code in the module is changing this? I would like to disable that portion while retaining the way the module allows selecting which content types are available to which groups.

Thanks.

@BeaPower, the problem you are having may be resulting from this. If the new posts default to public they will be visible in all groups and outside groups. You cannot see this on the default http://example.com/admin/content/node view, but if you are using views bulk operations you can add a field to your view to display the public setting and display it as a column.

Sorry, I forgot to attach the screen captures for my comments in #41.

I can confirm #35 its not working for me

On a fresh D6 latest install with OG 2.1 i gave a groupadmin permission to create content type X, in OG seperate i unmarked type X, making it unavailable for a grouptype.

However in the groupdetail block of the same grouptype i still see type X being able to be created.

I think i get the picture what the og_separate_groups. module does.

After enabling the module, site admin can decide which of the grouppost should be private.
So leaving a grouppost unmarked in the settings/og_separate ui will make grouppost private.
Saying "Audience: Show this post in these groups. This post will be private." no the node edit form for that grouppost type.

However i am more looking for a function where i can decide which grouppost contenttypes will be available in the groupdetail block.

note:it should be possible to let groupadmins post different contenttypes as groupmembers.
Depending on the contenttype groupadmins of a certain contenttype should be able to
post different posttypes then groupadmins of other contenttypes.
Same applies for groupmembers.

Hope this makes sense

The function i actually was looking for is totally covered in a hacked version of OGUR.
The module gives default role to a groupadmin or groupmember per groupcontenttype!

A patch is missing though...

http://drupal.org/node/837866#comment-3283030

subscribing

subscribing.

I've made a few modifications to ethangj's module and started a sandbox project

Two major differences:

• the module now generates an alternate group details block, entitled 'OG Details w/ Restricted Create Links' (very creative, I know).
• I've stripped the module down to include only one core function: permitting the restriction of group post types per group type

I plan to make further modifications to it, but I'm still familiarizing myself a bit. I currently have plans to release this module only for D6.

Any progress on this?
I found nothing in the sandbox project.

You need to use git to download sandbox projects directly from the repository:
http://drupal.org/project/1222488/git-instructions

@madmatter23 And what about public check box?

My groups are now limited to certain content types, but still, I want to make few posts public and available to everyone, not just certain group.

Well.. looks like public checkbox was hidden by this line (og_post_group_types.module:55):

//force post to be non-public so that a group must be selected. 
//this is the essential mechanism for limiting post visibility by group type
$form['og_nodeapi']['visible']['og_public']['#type'] = 'value';

Well it does the job, but still.. admins or other users could be interested to post group node into public domain of the site..

By commenting this line down - everything works just fine for now or at least as I expected.

Consider this:

I had a few group posts that were made public by checking that "public" checkbox, after installing this module, I lost control over audience publicity control. The posts were always visible by everyone and I was unable to uncheck it for obvious reasons :)

madmatter23 sandbox worked really well for this situation. should be a contrib module!