Closed (duplicate)
Project:
Drupal core
Version:
8.5.x-dev
Component:
taxonomy.module
Priority:
Major
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
2 Nov 2016 at 17:48 UTC
Updated:
3 Oct 2017 at 11:11 UTC
Jump to comment: Most recent
Comments
Comment #2
wim leersSee #2808217-22: To be able to view Vocabulary config entities via REST, one should not have to grant the 'administer taxonomy' permission for an example of what the test coverage should look like.
Comment #3
swentel commentedI guess #1038330: Allow specific vocabulary permissions to work on vocabulary admin pages is related in a way.
Comment #4
dawehner#1038330: Allow specific vocabulary permissions to work on vocabulary admin pages will fix indeed the underlying issue, but we maybe have to enlarge our REST test coverage for that.
Comment #5
Yasiru Nilan commentedI'm actually new to drupal development. Where actually this change is required?
A file may be.
Comment #6
wim leers#1038330: Allow specific vocabulary permissions to work on vocabulary admin pages hasn't been touched since September 2012. That's approaching its fifth birthday. I don't want to wait for that.
I'd actually say this is probably blocked on #2808217: To be able to view Vocabulary config entities via REST, one should not have to grant the 'administer taxonomy' permission to set a precedent.
This is definitely not novice in hindsight. Sorry, @Yasiru Nilan!
Comment #8
berdirI posted a detailed overview of all related issues that we have around this topic in #1848686-179: Add a dedicated permission to access the term overview page (without 'administer taxonomy' permission) (#179 if the link does not work).
That issue adds a create permission and also updates the term REST coverage for terms to use those permission. We could either remove the REST changes from there and do it here or close this as a duplicate of that issue. Leaving at postponed for now.
Comment #10
wim leersThis is exactly what #1848686: Add a dedicated permission to access the term overview page (without 'administer taxonomy' permission) did! It did so for all cases: "create", "update" and "delete"! You can see the consequences for the Taxonomy Term REST test coverage in the relevant hunk from that issue:
🎉