I have all working fine before install OG User Roles. But I want to make a default role for the registered user by invitation.
So, the Drupal admin can do everything, the Client (created by the Drupal admin) can create groups, projects, cases and invite new users. The invited users by the Client can only post cases and comments.
When I install OG User Roles now nobody can create Cases, the Drupal admin, the client or the new default user.
I got this error after submit the new case:
* warning: Invalid argument supplied for foreach() in /home/#####/domains/mydomain.com/html/modules/og_user_roles/og_user_roles.module on line 1613.
* You do not have permission to post this content type (casetracker_basic_case) into Group: mygroup (1)
My ease solution is to make new registers with moderation by the Drupal admin, so he can assign the role manually, but would be nice make this automatic.
Thanks in advance
Comments
Comment #1
pivica commentedI have the same problem. But when I created new content type and configured case tracker to use it like case node type everything is working fine. I guess if i create new project type and use it instead of default case tracker project type that would also work.
Mine question is - is this normal? - that default project and case types are not working as expected and I have to create custom project and case types if i want to use case tracker with og and og_user_roles?
Comment #2
somebodysysop commentedSolution is in first post here: http://drupal.org/node/269697
Case tracker needs to return the correct permissions. This additional check is a drag, I know, but we have to have some way to protect against OG User Roles allowing users to post content into groups that they should not be able to post into.
Comment #3
pivica commentedSomebodySysop thanks for quick replay :)
But its not yet clear to me what solution should I take. Should I patch casetracker_basic.module like described in http://drupal.org/node/269697 or to create custom project and case types and stick with it?
Comment #4
pivica commentedOK I have patched casetracker_basic.module and now everything is working as it should. And also I think this is a better solution.
My only suggestion is to reopen http://drupal.org/node/269697 and suggest that this patch go into dev version of case tracker.
Comment #5
jmiccolis commentedHi folks, this issue seemed to have been spread out over a couple tickets and it's a bit difficult to follow what's what. If anyone is still interested in seeing a patch go into casetracker could they:
Thanks!
Comment #6
pedrorocha commented5.x version is obsolete and will not receive any updates, so i'm closing this issue