Problem/motivation:
Allow translators to translate every configuration, but don't give them access to the original config.
For example: A field is created with original translation en. The translators can translate the configuration in other languages, but unless they have manage field access they will not be able to edit the English label. We don't want to give translators access to the field settings because they can alter or delete the field.
Proposed solution:
Set the language for every configuration to zxx and allow config translation to be translated against the non-applicable language.
The patched attached removes the access restriction for locked language config translation.
Needs work
10.1 ✨
Last updated
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Reviewing MR 2797. Hiding files to avoid confusion.
Tagging for tests.
The new schema will need a post_update hook for existing sites. Also a test for that hook
Change record for the new route.
Thanks!