Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The Taxonomy Access Control module allows me to set taxonomy access, update, delete, etc. permissions to branches of a hierarchical taxonomy. I have the TAC module set to allow a user to create etc. on only 1 branch of the root level of the taxonomy.
Hierarchical Select is set to show this taxonomy on the blog creation form. Initially HS does the right thing: the dropdown list of the root level of the tax shows only the branch the user has access to. However, if the user hits then returns to the root level, the root level shows a list of all the branches on the root level of the taxonomy. The user is not supposed to have access to these and didn't before (s)he hit .
| Comment | File | Size | Author |
|---|---|---|---|
| after user hits add - bad.jpg | 16.21 KB | whyameye | |
| before user hits add - good.jpg | 15.33 KB | whyameye |
Comments
Comment #1
whyameye commentedSorry. Just noticed that some of the above comment did not show correctly because some of it was incorrectly interpreted as HTML. Here is the comment again with that problem fixed. Explanatory attachments are still in the previous comment:
The Taxonomy Access Control module allows me to set taxonomy access, update, delete, etc. permissions to branches of a hierarchical taxonomy. I have the TAC module set to allow a user to create etc. on only 1 branch of the root level of the taxonomy.
Hierarchical Select is set to show this taxonomy on the blog creation form. Initially HS does the right thing: the dropdown list of the root level of the tax shows only the branch the user has access to. However, if the user hits ADD then returns to the root level, the root level shows a list of all the branches on the root level of the taxonomy. The user is not supposed to have access to these and didn't before (s)he hit ADD.
Comment #2
whyameye commentedI have further narrowed down the problem: this issue comes up when a term is given list permission and not create permission by TAC. It appears that initially HS lists the nodes based on create permission. After clicking on a taxonomy or clicking add, it lists the nodes by list permission.
Comment #3
wim leersHierarchical Select doesn't support Taxonomy Access Control yet. If some things work already, then it's accidental. Patches are accepted. I won't fix this myself, due to lack of time and because there are so few people using TAC.
Feel free to reopen this issue.
Comment #4
gooddesignusa commentedsubscribing. I really like the ability in Hierarchical Select to only let the user select the deepest. I would really like to use this module with one of my sites but I need TAC. Might look into getting someone to patch this if I have the $