[More Info] Site Administrators see all content types in groups
| Project: | Content Type Administration by Organic Group |
| Version: | 5.x-1.3 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I am currently using og_user_roles, og_subgroups, acl, content access, and content_type_admin. first off, thank you so much for your module, it is wonderful! I have a site which requires content types to be restricted per groups. There is a mix of public and private groups. I the private groups there are many times where a user will be a member of multiple groups, but his/her role or function will change per group - hence the use of og_user-roles. But another need we have is to restrict content types to those groups to avoid any confusion to end-users and avoid any possibility of a private post ending up in the wrong group. This has required us to create content types per group, sometimes multiple content types depending on the groups needs/function. So, we have alot, I mean alot of group specific content types. the problem we are having is that as a site admin user I see every single content type in the group details block although restrictions are applied to site users with group roles. This makes it a little tedious as an admin working with multiple groups. I would like the same restrictions of the details block as an admin as group members have. Could you assist?
-Jen
Ps Thanks again for this module, it is a life saver!
#1
Hmm, I can see your problem. I too have a site where groups have slight variations on a similar content type. It may become burdensome in the future for me as it seems to be for you now. So I may add a checkbox to apply group restrictions to the admin user in the future. For now, you can modify the code fairly easily. Look for instances where I check if
$user->uid == 1. Most of them simply kick you out of the function, bypassing the restrictions that this module employs. If you comment out the check (usually an 'if' statement and a line or two of code such as 'return;' or 'continue;'), then there will be no special case for user 1. You might have to assign roles to your admin user though. I don't recall specifically.In the cases where I'm not specifically checking $user->uid, those will be harder to modify since I'm probably checking a permission and the user module itself grants all permissions to user 1. But I may not have done that. I'm not in front of the code right now, so I don't recall what checks there are in place.
In any case, I hope that answers your question. And make sure to keep a log of your changes so you can apply them to any updates you might make to this module in the future. Better yet, keep all of your projects in 'subversion' or some other version management repository.
#2
thanks so much, I'll test out the changes and let you know how it goes. I can not write code myself, but have modified so much of it up this point with Drupal I think I can swing this one as far as commenting out user 1 checks. If it works out, would you like me to upload the patch file? If not, would you mind assisting in the other aspects of the code? I realize you are busy and have a lot on your plate with this and your other modules, so I appreciate all your help.
Also, while I'm thinking of it, assigning the admin/user 1 roles will not be a problem as I already have been doing that and assigining myself/user1/admin the groupadmin and group founder roles through og_user_roles, so that works out nicely.
thanks so much,
Jen
#3
Simply commenting out user 1 checks isn't something I need a patch from you for. When I do the change it will be more robust than that.
Anyway, if you run into problems, post them and I'll help as I can.
#4
thank you, I really appreciate all the help.
-Jen
#5
Did this work for you? I'm switching this to a feature request if it did and postponing it so I don't lose it.
#6
Do you still require assistance ?
#7
As there has been no response for more than two weeks i will close this feature request. Please
reopen if you need assistance.
#8