Closed (fixed)
Project:
TMGMT DeepL Integration
Version:
2.2.x-dev
Component:
tmgmt_deepl_glossary
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2023 at 16:06 UTC
Updated:
11 Dec 2023 at 13:29 UTC
Jump to comment: Most recent
Comments
Comment #2
steffenrComment #3
steffenrComment #4
steffenrComment #5
steffenrComment #6
steffenrComment #7
mrshowermanExcellent, that's exactly what I need 👏🏼
Comment #8
steffenrComment #11
steffenr@mrshowerman
The changes can be tested in the latest 2.2.x-dev release of the module.
I've also added a new permission access deepl_glossary overview to simplify access handling.
Two hook_update_n take care of updating existing user roles with the new permissions.
Feel free to test and give feedback.
Comment #12
mrshowermanNot sure if this is a bug or a misunderstanding on my side, but I had to grant the "administer deepl_glossary entities" permission along with "access deepl_glossary overview" and "edit deepl_glossary glossary entries" in order enable editors to access and edit glossary entries.
While editors aren't able to edit the glossary entities (which is good), I had expected that only the last two permissions would suffice, and the "administer" term sounds more powerful than what I wanted to grant them 😉
Comment #13
steffenrI'll have a further look.
While testing on my local environment it was sufficient to just set access deepl_glossary overview and edit deepl_glossary glossary entries..
Comment #14
steffenr@mrshowerman
Are you sure, that your permissions are configured correctly?
I just did a test on a blank D10 site with just tmgmt and tmgt_deepl installed and got access to the deepl_glossary overview page without the need of the administer permission.
The following permissions are granted to the role content_editor
Comment #15
mrshowermanI installed the module on another site, and there the "access overview " and "edit entries" permissions were sufficient. So it must be a different issue on the first site, will have to find out myself.
Sorry for the noise, I think this is ready.
Comment #16
steffenrThanks for testing the new functionality.
A new 2.2.0 release was just released.