| Project: | OG Access Roles |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | reviewed & tested by the community |
Issue Summary
I'm back.
My request may be like the one in http://drupal.org/node/697366 but there was more described in that so I thought I'd try to explain what I am looking for.
I understand the use case for the module as it but need different settings.
I would like to have the option to make the function provided by og_access_roles configurable so it can be set to available only to group admins. If this check box was left blank the module would work as it currently does, but if it were checked for group admins only then only they would see the roles that can be granted access to the node.
This would be very handy for groups that are otherwise private to make some of their content available to specific roles site wide but have that controlled by the group admins.
Thanks,
Izzy
Comments
#1
On thinking about this further, it would probably be easier to implement and maybe even more versatile if the module had its own user permissions and could be available to specified roles.
This would make it easier in cases where users may be members of more than one group and not necessarily admins of all.
The idea of permissions for the user access roles module was part of the granularity requested in the earlier issue, http://drupal.org/node/697366 so I may indeed have created a duplicate.
Thanks,
Izzy
#2
I realize it's a holiday weekend and don't expect people will be spending as much time here.
I have not written any code modifications for Drupal yet and I'm just trying to figure out what it would take to add user permissions to this module.
From what I can figure so far it seems like it needs a function implementing hook_perm() like,
function og_access_roles_perm() { ... ; }
And then needs a conditional added.
Am I on the right track?
#3
+bump
I'm wondering if anyone can help me on this. Thanks.
#4
@izmeez - the initial issue makes a lot of sense. The module should provide a way for only group admins to see the role checkboxes on group posts. That feature would have a good chance of making it into the module because it is well defined and seems universally useful.
The user permissions idea needs to be better defined -- I'm not sure what exactly you're asking for there.
It might be good for you and the author of #697366: More granularity and default settings to get together and see if you can come up with an idea that would work for both of you.
Sorry I haven't been more active here.
#5
@marcp Thank you for your reply.
Yes, I had wondered if I should have posted to the other issue but it describes several things and I didn't want to hijack it. I have put a brief note there linking to this issue. I hope that helps.
I will attempt to clarify my thoughts.
I realize I have suggested two things and as I have been exploring this I realize they open up different possible applications. They are:
1. Add user permission for OG access roles.
2. Add option to make OG access roles only available to group admins.
Currently, it is the first of these options that I need for an application. I also think the first option adds tremendous versatility. It would allow the site to be configured such that specific site roles would have access to og access roles without it being necessarily visible to all users. With multiple groups it keeps the content creation form simple for each group and yet allows specific roles to be able to expose the content of their group to other site-wide users based on roles.
The second option to make OG access roles only available to group admins would also be helpful for different cases and still would be useful. However, it would not be a good substitute for option one in some cases where users need the ability to expose content site wide but not acquire group admin privileges in the process. Obviously, if the second option was the only one available it could be used but may not be ideal for some cases.
Thanks very much for your time and consideration.
Izzy
#6
This may not be the best way to do this but I have gone ahead and created a patch to add user permissions to access og_access_roles
This specifies which site roles can see the extra options on the node edit form.
#7
Just changing the status to "needs review".
Thanks.
#8
@izmeez - thanks for the patch in #6 - we've been buried under some other work.
We appreciate your patience, and will try and look at this soon.
#9
Stumbled upon my patch from last summer and wondering if anyone can review?
Thanks.
#10
+bump patch for review, anyone ? any thoughts ?
Thanks.
#11
+bump Wondering if anyone has a chance to review this? Thanks.
Izzy
#12
Hi,
I'm using it on one of my sites. It works great. Thank you. I'm starting to look at how I can use views-bulk-operations to make mass og_access changes to nodes in private groups. Any ideas?
Thanks, Jim
#13
@jwilde Thanks for the feedback. Do you think you can change status to RTBC ?
As for
you could start this question as a new support issue. Thanks.
#14
This patch worked for me. Thanks
#15
I have changed the title in the hope to make this clearer.
The patch in comment #6 simply adds user permissions to the og_access_roles module.
As explained in comment #5 this allows only specified roles to use the og_access_roles settings rather than having this available to all authenticated users. This is useful for a variety of use cases.