Posted by stephtek on November 5, 2009 at 12:20am
Jump to:
| Project: | Taxonomy Access Control |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (cannot reproduce) |
Issue Summary
I was wondering if it is possible to set it up so that when more than one taxonomy term is selected per node that the users assigned the corresponding roles can see content from all terms selected.
I cant seem to make it work. When I select more than one taxonomy term for a node it doesnt display for any roles.
This is fairly urgent. Any help would be greatly appreciated.
Comments
#1
This is fairly urgent, Will pay for help if necessary.
thank you :)
#2
could you elaborate on 'corresponding roles' ??
perhaps a link might illuminate what you are trying to do.
when you say 'see' -- do you mean ability to access, or that the node appears in a specific list that is fed to them?
#3
An example...
You set up a content type - Teams only Sharable Resource.
You have a taxonomy - Authenticate Team Content (i.e. who do you want to access this particular content type).
So under Authenticate Team Content you have your terms / team names... IT ; Care ; Sales ; All Teams Access
Which correspond to the appropriate roles / groups in Drupal...
You allocate appropriate permissions in TAC...
You create a new Teams only Shareable Resource node content item and tick multiple terms (e.g. IT + Care )
The result is that only the creator of the content type can view/edit/delete...
However, if you tick only ONE term - IT then all the IT (term/role) people can view that particular node/content type.
Works fine for one term - tested fine on each term.
So the problem seems to be when you tick more than one term.
Does that make sense / more helpful ?
#4
Based on the explanation in #3, this sounds like it may be related to an issue in the 5.x branch: #301597: Prevent users from inadvertently un-tagging terms they don't have CREATE privs for?
Marked that one as duplicate.
Edit: for the record, the workaround I used for that issue for 5.x was to create a little custom module that denied everyone but content administrators access to nodes that were tagged with conflicting terms.
#5
#207447: i run in this inconsistency when I was plying with permisions is also related to this.
#6
I am unable to duplicate this problem in the current build of the module. It's possible it has since been fixed, or possible that it's a permissions configuration issue. Closing, in either case.
#7
The patch available in #881210: No list or create permissions on any terms may result in incorrect use of default on save should resolve any remaining problems like this. If you still encounter this bug or anything like it, please test the patch from that issue with the latest dev build of TAC. Direct link to patch:
http://drupal.org/files/issues/tac_881210-9.patch