I am using some other Node Access module for fine-tuning ticket visibility. For example, using Taxonomy Access Control users can set a tag at ticket-creation time to limit visibility to a set of users, and so on..
But, Support module's own "Access Client-name tickets" permission setting overrides any other visibility restrictions, and grants view permissions anyway. It should be implemented the other way around: deny if this permission is unset, don't deny (or do nothing, leave it to node-permissions to handle) visibility.
Thanks for the AWESOME module!
Comments
Comment #1
sly5 commentedSorry for the fragment: I meant to conclude:
".. don't grant visibility otherwise [if the view permission is on]. "
Comment #2
sly5 commentedI just found one work around, although it might not be the most correct fix:
There is only a single line to change:
Comment #3
sly5 commentedbump
Comment #4
jeremy commentedCleaned up hook_access() and improved support module to respect other Drupal access control modules:
http://drupalcode.org/project/support.git/commit/fd7ce22
Needs to be ported to the 7.x branch.
Comment #5
izmeez commentedThe way this works with organic groups 6.x-2.x is great. Thanks.
Comment #6
izmeez commentedOn testing this further with organic groups it works when users are accessing the support ticket node(s). Users cannot access nodes within the group unless they also have support ticket "client" access.
It also works with Drupal search.
However, it does not restrict the user from seeing the teasers or titles of tickets in views such as recent posts.
I have changed the status to needs work rather than opening a new ticket.
Thanks.
Comment #7
izmeez commentedI'm again wondering if the ideas used in the views_unpublished module may be helpful to those with the coding expertise, http://drupal.org/node/768354
Does the order of access control modules make a difference?
Comment #8
bdragon commented@#6: Please see #818250: Support ticket comments displayed in the 'Recent comments' block even when user don't have permissions, I think...
-------
Ported to 7.x-1.x.
http://drupalcode.org/project/support.git/commit/4178c19e3c8b917b07d972c...
Comment #9
izmeez commented@bdragon re: comment #8 the link to the issue with recent comments may be a similar problem and may help in finding a solution but this problem with the titles and teasers showing in views is a problem. Yes, a work around is to change the view(s) and exclude tickets but is there a better solution? I've put this back to "needs work".
Comment #10
bdragon commentedI just rewrote the query altering and fixed an issue where people with create ticket permission were not getting filtered down to their clients properly.
I will be releasing beta1 shortly, would appreciate feedback on whether or not it helps.
Comment #11
izmeez commentedLooking at the commit log it looks as though this is committed to the 6.x-1.x-dev branch so I will give it a test.
Comment #12
izmeez commented@bdragon, Yes this seems to have fixed it for support-6.x-1.x-dev. I haven't had a chance to do extensive testing but views including titles and teasers now seems to respect the access grants for og.
Comment #13
jeremy commentedGreat news! Marking as fixed.
Comment #15
ramirez.gerardo commentedAll,
I've created a D7 module to help the co-existance between Organic Group and the Support modules. Basically the module now allows for members of the same group to view each others support tickets. I'm new to community contributions so I was only able to create a sandbox version... Please download and test the module here:
http://drupal.org/sandbox/ramirez.gerardo/1741272
Comment #16
jeremy commentedPlease open a new ticket to track this; it's not helpful to tack it onto a closed, previously fixed ticket.