OGUR + Voting API/Flag
| Project: | OG User Roles |
| Version: | 6.x-1.5 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi all,
need help with this. Probably I'm missing something here. Any directions appreciated:
Drupal 6 + OG + OGUR + Voting API (Extra Voting Forms) + Flag
"Default Group Role for new group administrator" set to "groupadmin" which is allowed to give points thru Voting API and flag content (of group post type) thru Flag.
New group administrators are assigned "groupadmin" role upon promotion by group founder but then they cant vote/flag content in the group until site admin assigns "groupadmin" to them manually thru their profile. After that it appears they have site-wide rights to vote/flag in any group which is not acceprable either.
Am I missing something about OGUR access rights mechanics? That seemed to me it was quite a simple task to limit vote/flag privileges to group admins in that way but now it looks like the things dont work as I expected them to?
Many thanks in advance.
#1
I don't use the voting api or flag. I can tell you that OGUR only provides the permssions of group roles while in group context. The problem here clearly is that Voting API (Extra Voting Forms) + Flag does not support OG group contexts, therefore your groupadmins won't have the permissions of the group role(s) you have assigned.
To verify this, you can use the OG User Test setting to output debug info to a table while you attempt to have your groupadmin access Voting API (Extra Voting Forms) + Flag functions.
#2
Thanks Ron. Got it.
#3
After the rise of the rewritten OGUR 4.x for Drupal 6, in which many unrelated features of OGUR were removed, and nearing a release of Drupal 7, I'm closing down old issues.
#4
It appears that this is fixed.
The person who changed the status of these issues to "won't fix" was not authorized to do so: http://drupal.org/node/352139#comment-2352234
OGUR 6.x-1.x will continue to be maintained by me.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.