Taxonomy access fix

Synopsis

Taxonomy Access Fix module extends access handling of Drupal Core's Taxonomy module.

Taxonomy Access Fix 4.x

• adds several permissions to view published and unpublished term names.
• adds several permissions to view published and unpublished terms.
• adds several permissions to reorder terms in vocabularies.
• adds several permissions to select published and unpublished terms in autocomplete widgets of certain entity reference fields.
• adds several permissions to view vocabulary names.
• adds several permissions to reset vocabularies.
• adds permissions to create, delete or edit terms in any vocabulary.
• removes vocabularies the user doesn't have permission to either create, delete, edit, reorder terms in or reset from the vocabulary overview page.

Note: The actual changes to access checks and permissions provided by the module may differ between major versions. For detailed information about the features provided by your major version, refer to the README file of that version. Unless otherwise noted, information on the project page applies to the latest branch with supported stable releases.

Use cases

You need more fine-grained permissions for Taxonomy terms than those provided by Drupal Core, e. g. you want only certain roles to be able to view terms in a vocabulary.

Requirements

This module depends requires no modules outside of Drupal Core.

Usage

Change permissions as needed on the Manage -> People -> Permissions page. Per-vocabulary permissions can also be managed using the Manage permissions tab of a Taxonomy Vocabulary.

A module can't add permissions on behalf of another module, so the extra permissions are listed under Taxonomy Access Fix and not under Taxonomy.

Access to vocabulary overview page

To access the vocabulary overview page for a vocabulary, users must have permission to either

• create, edit, delete, reorder terms in or reset that vocabulary in addition to the Taxonomy module's permission to "Access the taxonomy vocabulary overview page".
• to "Administer vocabularies and terms".

Create, edit or delete terms in any vocabulary

Per-vocabulary permissions to create, update or delete terms are provided by Drupal Core. Taxonomy Access Fix additionally provides permissions to create, update or delete terms in any vocabulary.

View term names / View terms

The per-vocabulary "VOCABULARY: View published term names" permission will allow users to view the term name of published terms. To view term names of unpublished terms, users will need the per-vocabulary "VOCABULARY: View unpublished term names" permission or permission to "Administer vocabularies and terms" provided by Drupal Core.

The per-vocabulary "VOCABULARY: View published terms" permission will allow users to view published terms. To view unpublished terms, users will need the per-vocabulary "VOCABULARY: View unpublished terms" permission or permission to "Administer vocabularies and terms" provided by Drupal Core.

Users having permission to "view terms" do not have permission to view the term name unless they also have a permission required to "view term names".

Permissions to view any terms and view any term names are also available both for published and unpublished terms. They will grant access to view terms or term names for any vocabulary.

View vocabulary name

The per-vocabulary "VOCABULARY: View vocabulary name" permission will allow users to view the name of the vocabulary. There is also a permission to "view any vocabulary name".

Users having permission to access the overview page of a vocabulary (i.e. the page that lists all terms in a vocabulary) do also have access to view the vocabulary name even if they don't have permission to "VOCABULARY: View vocabulary name" or "View any vocabulary name".

Reorder terms

The per-vocabulary "VOCABULARY: Reorder terms" permission will allow users to change the order of terms.

A permission to "Reorder terms in any vocabulary" is also available.

Users with permission to reorder terms will not have permission to reset the term order to alphabetical, unless they also have permission to reset a vocabulary.

Reset vocabulary

The per-vocabulary "VOCABULARY: Reset" permission will allow users to access to the vocabulary reset form that resets the term order of the vocabulary to alphabetical order. If they also have the "Access vocabulary overview page" permission provided by Drupal Core, they will be granted access to the vocabulary collection page and the vocabulary overview page for the relevant vocabulary and the "Reset to alphabetical order" button on that page.
A permission to "Reset any vocabulary" is also available, that will grant access to reset the term order to alphabetical for any vocabulary.

If users don't have permission to access the vocabulary overview page, they will be redirect to the front page after confirming or canceling the reset operation. You can override the redirect by setting a suitable destination query string parameter.

Select terms

The module will replace the default entity reference selection plugin for Taxonomy Terms with an extended version that checks for a separate per-vocabulary "VOCABULARY: Select published terms" permission. To select unpublished terms, users will need the per-vocabulary "VOCABULARY: Select unpublished terms" permission or permission to "Administer vocabularies and terms" provided by Drupal Core.

Note: Users with permission to select terms will be able to see the term labels of those terms in the results of the autocomplete widget, even if they don't have permission to "view" those term names or terms. Only Entity Reference fields referencing Taxonomy terms using the "Default" reference method will honor this permission.

Permissions to select any term are also available both for published and unpublished terms. They will grant access to "select terms" for any vocabulary.

How to upgrade from 8.x-3.x

To upgrade from 8.x-3.x, please update to 8.x-3.3 first. Once you have applied the database changes, you should be able to upgrade to 4.x at any time.

Core compatibility and expected end of life

Disclaimer: EOL dates for branches are provided as a service to the community so that you can plan ahead and upgrade in time. They reflect our current plans. Unforeseen issues may arise at any time, that may result in a branch being unsupported earlier than expected. We will do our best to prevent this, though.

See also: Drupal core release cycle: major, minor, and patch releases

Related modules

• Use taxonomy_autocomplete_permission to add permissions for autocomplete/tag creation too
• vppr adds per-role access checks
• taxonomy_permissions restricts view access