Active
Project:
Taxonomy Permissions
Version:
7.x-1.0-rc1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Apr 2014 at 09:47 UTC
Updated:
11 May 2014 at 00:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
rsorokine commentedComment #2
salvisThank you for raising this issue, rsorokine.
I'm afraid your upload is not getting the attention it deserves because zip files (and other format that are not readable in the browser) are out of sight for most people.
At this point, withholding Taxonomy Permissions "View terms" permissions will effectively override core's "Administer vocabularies and terms" permission, but other aspects of administering a vocabulary remain available (and the user can even add terms that he cannot see afterwards).
Typically, core's Administer permissions are stronger and provide full access to the functionality that they cover. Making the "View terms" permissions override the "Administer vocabularies and terms" permission was an accident rather than a conscious decision on my part.
The question is: is it a feature or a bug?
In the former case we need not only remove the vocabulary from the admin/structure/taxonomy page, but also deny access to all pages under admin/structure/taxonomy/vocabulary_name.
In the latter case, we need to fix it and destroy potentially useful functionality for the sake of consistent behavior. Tough call...