Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Install
Works with Drupal: 7.xUsing Composer to manage Drupal site dependencies
Downloads
Download taxonomy_access-7.x-1.0-rc1.tar.gztar.gz
37.35 KB
MD5: b8ee44eb5de829c0df554934d540f9d8
SHA-1: 886e768165380f29cc8021c7c3497d3a4cf8d59e
SHA-256: 5991505ca8418f9ec4d66c06e159430c27b4b8c679c2bd360f679275087739bd
Download taxonomy_access-7.x-1.0-rc1.zipzip
41.67 KB
MD5: 43d7897cfe57360e388a24e0a27d1499
SHA-1: aa18f10937aea7995e99ba595ce877fd09b1fa64
SHA-256: e4cd90b711246e02fcbe235d6546af853adcc943df83a63063a90c5a61bcb911
Release notes
This is the first stable release candidate for Taxonomy Access Control in Drupal 7.
Important notes
- This release candidate requires Drupal 7.8 or later.
- If you previously installed any version of Taxonomy Access Control earlier than 7.x-1.0-alpha1, you must run
update.php
when installing this release candidate. - Be sure to clear your site and browser caches when updating from previous versions.
Changes since 6.x-1.3
- Several performance improvements.
- The Create permission has been renamed to Add tag.
- The List permission has been renamed to View tag.
- The Add tag permission for the vocabulary default now controls whether a role can automatically create new terms in that vocabulary in autocomplete (freetagging) fields.
- Term reference fields are automatically hidden if Add tag permissions do not allow the user to change the field value.
- Terms disallowed by the Add tag permission are disabled rather than hidden. See #1209154: Form UX: disabling vs. hiding disallowed terms for the reason this change was made as well as possible future improvements.
- The module's database tables and grant realm have been renamed.
- Administrative paths have changed.
For a complete changelog, see the git log.
Outstanding issues
All known bugs have been resolved. However, there is a Drupal core bug that may cause issues when a field with controlled terms is deleted from a content type:
#1065814: Content remains tagged with a taxonomy term (via the {taxonomy_index} table) even after its corresponding term reference field is deleted and purged