Closed (duplicate)
Project:
Content Type Administration by Organic Group
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
5 May 2007 at 00:39 UTC
Updated:
23 May 2007 at 22:23 UTC
Comments
Comment #1
rconstantine commentedBy "all users", I assume you mean all users within a particular group, correct? What it sounds like you want are almost like subgroups, or different roles inside of groups. This may be possible if you use the subgroup module. I don't recall the name of it, and I've never used it. You might also use it in conjunction with my "accounttypes" module and maybe even my "multiple mandatory groups by role" module. Account types lets you restrict which roles can be assigned to which people. People are assigned to account types first, then the roles they can have are restricted to those assigned to the account type. The other module enrolls and removes people from (mainly closed) groups based on their roles. So if you had a group called 'a', with subgroups 'b' and 'c', you could funnel regular users to 'a' and give them a limited set of content types to use. You could then assign some of those members to either 'b' or 'c' or both if you want to give them greater freedom. I think that would work, but I'm not sure about visibility of posts and whatever. You'll have to experiment. I know that people have talked about allowing group owners to assign roles that are only within that group, but I don't know if anyone has ever done it. If it comes to a point where I need this, I'll do it myself as another module.
I suppose another way to look at your request would be "content types by role". Interesting.
Wait a minute... I'll have to look at the code and try it out myself, but I thought that I had made it so the group owners could use all allowed content types, and then regular users could only use activated types. So try this: as admin, go into the admin group content type settings and allow all of the types you've listed. Then, as group owner, go into the group owner content type settings and activate only those you want your users to do, leaving those you want the owner to have private access to unchecked. Then as owner, see what comes up in your menu for adding group content. Report back here with your findings.
Comment #2
rconstantine commentedSince this functionality could be taken care of by this: http://drupal.org/node/133650, I'm marking this post as a duplicate.
Comment #3
rconstantine commentedI'll add this same note to the other issue as well...
It seems group admins CANNOT currently use ALLOWED and non-ACTIVATED content types. I'll change that.
Comment #4
dexdes commentedYes, I had a go at it and came to the same conclusion. If you could make the changes to allow this then that would be great. The discussion about even more granular control with roles would be an even better solution - though its not something I myself know how to implement though would be very interested if this might be worked on in the future.
Comment #5
rconstantine commentedFixed so that group admins can use ALLOWED but DEACTIVATED content types. This means that group members can view content that only the group admin can create. Hopefully this works as intended. Group members can still create ACTIVATED types that are activated by the group admins.
Look for an update to the dev branch with this included soon.
So if you want, for example, the blog content type to be available only to group admins, you would ALLOW it and then the group admin simply would not ACTIVATE it in their own group context. If you aren't giving group admins control of their content types (via the "Disallow changes by all group owners" checkbox), then you have total control over this. Perhaps in the future I should add a third column of checkboxes in the "Assign Content Types" tab which locks each type for use only by group admins. The column would be called "Group admin only" and would go between "Allow" and "Require". It would be the same as locking it to ALLOWED and DEACTIVATED.
Also, my changes should also allow the site admin, user 1, to create any content type anywhere, both inside and outside of groups.