There are still three routes with requirements
_permission: 'administer taxonomy' 'administer taxonomy'
instead of
_entity_create_access: 'taxonomy_term:{taxonomy_vocabulary}'
This was addressed in [#2991079] with a patch for 8.x.1.x.
#17 in this issue also has a patch for 2.x but it does not apply any more.
Most of the changes from this issue made it into 2.x - but not all.
Change requirements of the three routes to
_entity_create_access: 'taxonomy_term:{taxonomy_vocabulary}'
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | taxonomy_manager-permissions-per-vocabulary-2.x-3259399.patch | 1.36 KB | gngn |
Comments
Comment #2
gngn commentedPatch as proposed above.
Comment #3
vladimirausTesting
Comment #4
gngn commented@VladimirAus did you tests had any results?
(not pushing, just curious)
Comment #5
dcam commentedI just installed the D9 version for the first time. I was taken aback to see that I would need to grant admin permissions to content editors in order for them to see the term lists. So this feature gets a +1 from me.
I applied the patch to our dev site and it granted the ability to access the three listed routes without the need for the
'administer taxonomy'permission.Comment #6
vladimiraus@gngn I went AWOL for couple of month.
@dcam - thanks for testing
Back now. Planning to commit it soon.
Comment #7
alfattal commentedThis patch would also grant permission to administer Taxonomy Manager and not only to (Access taxonomy manager list) which is not desired for editor role. Editor role should only be able to make changes to the content and NOT make any changes to system config that will result in config mismatch. Is there any way to separate these two permissions?
Comment #9
vladimirausThank you. Committed.