| Project: | Content Type Administration by Organic Group |
| Version: | 6.x-1.2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
In the admin option "Disallow changes by all group owners"
It states that this behaviour:
"Hide the group owner interface so they can't change their group's settings. This has the effect of setting all ALLOWED content types to ACTIVATED since the group owner will no longer be able to set them. This affects all groups. Once checked and saved, unchecking (and saving) will not DEACTIVATE any type."
I would like to be able to override this particular bit:
"This has the effect of setting all ALLOWED content types to ACTIVATED since the group owner will no longer be able to set them. "
I don't want the group owners to be able to override this behaviour, nor do I want them to activate the types. I essentially want a load of read only groups. Can this be set as an option or override?
Thanks, Stephen
Comments
#1
You misunderstand the option - or maybe the module. If the admin is creating the content, then you don't need to set any content type to ALLOWED, which in turn won't set any to ACTIVATED. That would be a READ ONLY group. If that's not what you want, then why have a bunch of content types that can't be used? If you use them elsewhere, then perhaps you need to consider copying them into READ ONLY versions specifically for those groups, then don't ALLOW them. If you have just a few content types, that's easy.
In any case, the point of this module is to ALLOW users to create content, but limit where - and it does that. Your idea is to PREVENT content creation in some other fashion that I don't think is in keeping with the design of this module.
Best of luck with your project in any case.
#2
"If the admin is creating the content, then you don't need to set any content type to ALLOWED, which in turn won't set any to ACTIVATED. That would be a READ ONLY group."
This is not the behaviour I am seeing.
Sitewide - all content types set to allowed. None to activated.
-- Scenario A --
Default: Allowed - no content types; Activated - no content types
Group manager can NOT create content types.
Members can NOT create content types.
-- Scenario B --
Default: Allowed - all content types; Activated - no content types
Group manager can create content types.
Normal members can create content types.
What am I missing?
#3
Scenario A is correct. When I was referring to admins, I meant site admins, not group admins.
Scenario B looks screwed up in your case, unless you've checked the box to disallow changes by the group manager, in which case Allowed content types become Activated.
Is there a reason you can't instruct group owners to not mess with the...
wait a minute. Are you the guy that emailed me? I believe I already provided a solution to changing the code to get it to do what you want, right?
Let me know.
#4
Yes I am:
1) we're testing the patch to restrict the changes that the group owner can make - this fixes another problem;
2) the issue above relates to the fact that it seems impossible to use this module to make a group read-only except for to group admins. Quite simply, we're looking for groups where group admins can post, members can not. Unfortunately neither Scenario A or B solves this need. Is this the correct behaviour?
#5
@Ryan
This looks to be site specific issue which has gone offline so ill close this issue .
#6
#7
I'm reopening the issue as feature request.
I guess the current implementation of the "Disallow changes by all group owners" option could be enhanced keeping the current functionalities.
Currently enabling the option, set "all ALLOWED content types to ACTIVATED" remove any difference between users: group admin and regular user can now post any allowed node type; in some way the side effect of this (expected by design) is raising user's permissions.
I guess could be useful to maintain the difference between "ALLOWED" and "REQUIRED" so that setting the option only remove the setting page on groups but still allows group admins (and only them) to create "ALLOWED" content.
This means for site admins (i.e. users with ''administer og content types'' permission) the possibility to differentiate which content is available for all users and which is available only for group admins using this module, while the current implementation is still available simply selecting the "REQUIRED" option. It simply remove the "Content Type" tab keeping the module functionality (content ALLOWED only for group admins, REQUIRED for all users).
The attached patch implements this feature.
If this sounds useful we can implement the update hook to keep the exactly same behavior on existing sites (i.e. if "Disallow changes by all group owners" set required on allowed node type).