The module provides a permission and handling to allow users (usually site builders) to edit translations of configuration that they already have edit access to. While Drupal Core already provides translatability using the config_translation module, a user needs the translate configuration permission:

Translate configuration
Translate any configuration including those shipped with modules and themes.

This is awesome, until you have configuration that you don't want your users to be allowed to translate as this is an all-or-nothing type of permission. This module provides the additional "Translate editable configuration" (translate editable configuration) permission, which allows the user to add and edit translations on any config translation routes where they can already edit the original configuration. This includes config provided by core, contrib or custom modules.

Project link

https://www.drupal.org/project/config_translation_access

Git instructions

git clone --branch 1.0.x https://git.drupalcode.org/project/config_translation_access.git

PAreview checklist

http://pareview.net/r/78

Comments

ckaotik created an issue. See original summary.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: [D8][D9] Configuration Translation Access » [D9] Configuration Translation Access
Issue summary: View changes
Status: Needs review » Needs work
Issue tags: +PAreview: project created less than ten days ago

Thank you for applying! I added the Git instructions for non-maintainer users and the PAreview checklist link. Reviewers will check the project and post comments to list what should be changed.

If you haven't done it, yet, please check the PAreview report and fix what needs to be fixed. There could be some false positives; verify that what reported is correct, before making any change.

ckaotik’s picture

ckaotik
Primary language German
Location Berlin
commented
Status: Needs work » Needs review

Thanks for running PAreview. I've updated the code accordingly, except for the branch name message wich I believe to be a false positive:

It appears you are working in the "1.0.x" branch in git. You should really be working in a version specific branch.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Yes, it's a false positive because it doesn't consider semantic versioning tags. PAreview expects tags to start with a number for the Drupal version with which the module is compatible, such as 8.x-1.x.

ckaotik’s picture

ckaotik
Primary language German
Location Berlin
commented

Is there anything I can do to move things forward?

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Needs review » Fixed
Issue tags: -PAreview: project created less than ten days ago

Looks good to me!

Thanks for your contribution, Anne!

I updated your account so you can opt into security advisory coverage now.

Here are some recommended readings to help with excellent maintainership:

You can find lots more contributors chatting on Slack or IRC in #drupal-contribute. So, come hang out and stay involved!

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks to the dedicated reviewer(s) as well.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.