Closed (fixed)
Project:
OG User Roles
Version:
5.x-3.3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jun 2008 at 09:18 UTC
Updated:
25 Oct 2008 at 16:59 UTC
If you use the default content types, you'll have problems with og_user_roles as explained in http://drupal.org/node/267117#comment-879548 not sure if this is a casetracker bug or an og_user_roles one.
Solution is to add the following code to casetracker_basic.module
function casetracker_basic_project_perm() {
return casetracker_basic_perm();
}
function casetracker_basic_case_perm() {
return casetracker_basic_perm();
}
Comments
Comment #1
attiks commentedcreated bug report in og_user_roles as well: http://drupal.org/node/269699
Comment #2
somebodysysop commentedIf you post an issue in 3 different places, it's kind of hard to respond. So, let's stay here for the time being until we figure out the correct place to be.
With respect to the actual error in og_user_roles on line 1613:
We are trying to get the permissions that the module says allows you to create this node type.
Apparently, the standard method for doing this:
$perms = module_invoke($module, 'perm')does not return anything for the casetracker_basic_case.module. Hence, the error.So, what we need is to know how to get the module's permissions so we can figure out whether someone with an OG role can post to it or not.
Comment #3
attiks commentedProblem is that casetracker_basic_case and casetracker_basic_project aren't recognized as regular nodes, so you don't get the regulare permissions like you get for other content types (create xxx content, edit xxx content, edit own xxx content) and apparently og_user_roles assumes that the nodes use this permission system. I'm afraid that other modules will face the same problem.
I think the easiest is to add the code as outlined in the description, this will solve the problem. Probably there's a cleaner solution to it, but I'm to tired for the moment :/
Peter
Comment #4
RAFA3L commentedSorry for the long time, I'm newbie with drupal and I don't know how I can get notify for each replay.
Well, I discover that the problem is if you use the original Case node, I create a new node and call it Ticket and the problem is gone.
Regards
Comment #5
somebodysysop commentedThen, let's say this is closed for now. The solution, I believe, is for the case module to return the correct permissions.
Comment #6
pivica commentedAbove patch in casetracker_basic.module problem fixes problem with adding default cases and project types to groups.
But I am facing one more problem with og_user_role. 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.
Comment #7
tborrome commentedSame problem here.
Is this og_user_roles problem or case_tracker?
since no response from case_Tracker project, can og_user_roles provide guidance on how to correct this behavior? need to get case_Tracker working with og_user_roles.
Recap: User is granted "access case tracker" role through configure member roles in a group. when case_tracker is accessed, "/casetracker/cases", shows "Access Denied".
Comment #8
somebodysysop commentedThe solution is in the very first entry in this issue. OGUR relys on modules to return the correct permissions
Solution is to add the following code to casetracker_basic.module
Or, does this not resolve your issue?
Comment #9
tborrome commentedno that doesnt, that sets permissions on the nodes - case and projects, and I can get that to work by creating my own node and setting member roles for those nodes.
The "access denied" issue for the case tracker seems more related to view permissions. when case_tracker page is accessed, 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.
Comment #10
somebodysysop commentedThen, you have a different problem. This particular issue is resolved and closed. You need to create a new issue for this. I use case tracker so I'll poke around a bit and see what I can find.
Comment #11
tborrome commentedok thanks, I have created a separate issue:
http://drupal.org/node/326055