- Issue created by @vermario
Currently, when you install the module, each of the existing taxonomy vocabularies will get two new fields that are used to associate users or roles to the terms for access control.
Also, when you create a new taxonomy vocabularies, the fields are added automatically.
This might not be desirable, and the user might want to instead control which of the vocabolaries are used for access control individually.
We could change the current implementation to add a checkbox in the vocabulary configuration form to activate or deactivate the functionality.
* Adding a checkbox to include a vocabulary in the access control functionality
* Adding a confirmation form when a vocabulary is no longer marked as used for access control (warning about what will happen)
* Trigger (or mark as needed) the recalculation of access rights when a dictionary is deactivated for access control
* Third party settings seem to fit what we need to do, associating an additional property to the taxonomy dictionary entity. These can be added to the config page of taxonomy dictionaries
* Change the installation logic and related tests, no longer adding the fields automatically
* Add an update function for existing installations, where all existing taxonomy vocabularies that have the fields will get the new setting as active
* Review all code to make sure that only active vocabularies are taken into consideration.
Active
1.0
Code