- Issue created by @gr4phic3r
The current implementation of the SHS module requires users to have either the "edit terms in {vocabulary}" or "administer taxonomy" permission to create new taxonomy terms via the SHS widget. This prevents users with the more limited "create terms in {vocabulary}" permission from adding new terms. Additionally, there was an issue with multilingual term creation that could result in type errors when processing translations.
Configure a taxonomy field to use the SHS widget.
Assign a user only the "create terms in {vocabulary}" permission, without granting "edit terms" or "administer taxonomy" rights.
Attempt to create a new taxonomy term using the SHS widget.
Observe that the term creation fails due to insufficient permissions and that a multilingual-related error may occur.
This patch modifies the access control logic in the createTermAccess() method to also accept the "create terms in {vocabulary}" permission. With this change, users with limited permissions can add new taxonomy terms without requiring broader "edit" or "administer" permissions. Additionally, the patch fixes the multilingual issue in the createTerm() method by ensuring proper language handling, which prevents type errors when processing translations.
Perform code review and testing in various multilingual environments.
Update or add relevant unit/functional tests.
Verify and update documentation regarding permission configuration and multilingual handling.
Ensure no regressions occur in other parts of the SHS module.
There are no changes to the user interface. The patch only affects internal access control and multilingual logic.
There are no changes to the public API; the modifications are confined to internal permission checks and multilingual handling within the SHS module.
No changes are made to the data model or entity definitions.
Thanks for this great module and thanks to AI for writing this Issue and fixing the code :)
Active
3.0
Code