Restrict Content Types by OG Type
ezra-g - June 1, 2007 - 02:04
| Project: | Content Type Administration by Organic Group |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed |
Jump to:
Description
Do you consider it within the scope and would you support a patch to this module to allow administrators to define allowed content types by group type?
That way all OG Nodes of a certain type could contain only certain node types. I'm developing a site where OG's of several types are added regularly. It would make more sense to configure this way once rather than configure the available node types for each new OG every time one is created.

#1
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.
#2
I am able to program. I'll get more familiar with the module and see how difficult it would be to patch.
#3
subscribe
#4
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?
#5
I agree. This would be extremely useful.
#6
Any advance in this field? it would be usefull for me as well
#7
Definitely need this too.
#8
Any progress on this issue?
#9
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.
#10
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.
#11
@Ryan
This is a great idea.
I'm going to change the status to postponed and see if i can work on this post migration to D6.
#12
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.
#13
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.
#14
My primary reason to use this module is this specific feature.
#15
This feature is exactly what i need too, any progress?
+1 subscribe
#16
Related to this thread, please see my patch to og here:
#433884: Restrict posting to group admins - read only groups
#17
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.
#18
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?
#19
I would really like to see this as well.
#20
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.)
#21
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
#22
So to clarify is the feature request here that we should be able to specify the default content types for each group node individually when there are a collection of group nodes ?
Best, Paul
#23
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
#24
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.
#25
#23 and #24 is exactly what we've been looking for in og since we first started using it 2 years ago.
#26
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.