I am facing one more problem with og_user_role and case_tracker. I have user that is allowed to "access case tracker" while he is in some og. But when user click to "view all project cases" in some project that belongs to og he get "Access denied" error. Obviously case_tracker is not using og_user_module for "access case tracker" permission in some situations.

Steps to reproduce.
1. Configure role with "access case tracker" permissions (also add permissions for creating cases and projects).
2. Make this a configurable group role and assign it to group members using og_user_roles configure member roles.
3. Group members with this role will be able to create cases and projects but... when the Cases and Projects are accessed from the Case Tracker menu item in Navigation, its supposed to show a list of existing cases and proijects, but instead shows "Access Denied".

This occurs if roles are granted within a group. If roles are explicitly granted to the user (instead of group role), it works.

Comments

somebodysysop’s picture

That's because none of the Casetracker links, "Casetracker", "Cases" or "Projects", provide any OG context. OGUR can not provide access to a url that doesn't provide a group context.

What would be easiest would be to simply give all users the "access case tracker" permisson, and use your group permissions to control access; that is, if you belong to the group, you can see the content. If you don't, you can't.

If access needs to be more tightly controlled: You must belong to the group AND have an additional permission, then I would recommend using taxonomy to resolve this.

One other thing you might try is to add the group context to your casetracker links:

http://yoursite.com/casetracker/cases?gids[]=<your group id>
http://yoursite.com/casetracker/projects?gids[]=<your group id>
somebodysysop’s picture

Assigned: Unassigned » somebodysysop
Status: Active » Fixed

No user response. Assuming fixed.

tborrome’s picture

thanks, i will try those.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.