Problem/Motivation

We need to ensure users don't accidentally enable for translation the fields that are related to Lingotek metadata.

Proposed resolution

There is no way to define that a field should never be translatable, so our only option is an alter form hook for the language content settings.

Remaining tasks

Patch with tests.

User interface changes

The field Lingotek Metadata or Lingotek translation source are not allowed to be enabled for translatability.

API changes

None

Data model changes

None

CommentFileSizeAuthor
#2 2887613-lingotek-metadata-language-content-settings-2.patch5.68 KBpenyaskito
#2 2887613-lingotek-metadata-language-content-settings-2.only-tests.patch2.21 KBpenyaskito

Comments

penyaskito created an issue. See original summary.

penyaskito’s picture

penyaskito
he/him
Primary language Spanish
Location 🧑🏽‍🌾 Seville 💃 Andalusia, UTC+2 🇪🇺
commented
Status: Active » Needs review
StatusFileSize
new 2887613-lingotek-metadata-language-content-settings-2.only-tests.patch2.21 KB
new 2887613-lingotek-metadata-language-content-settings-2.patch5.68 KB

Added the hook_form_alter.

The last submitted patch, 2: 2887613-lingotek-metadata-language-content-settings-2.only-tests.patch, failed testing. View results

penyaskito’s picture

penyaskito
he/him
Primary language Spanish
Location 🧑🏽‍🌾 Seville 💃 Andalusia, UTC+2 🇪🇺
commented
Status: Needs review » Reviewed & tested by the community

Tests passed and failed as expected.

  • penyaskito committed af3ce03 on 8.x-2.x 
    Issue #2887613 by penyaskito: Ensure users cannot enable for translation...
penyaskito’s picture

penyaskito
he/him
Primary language Spanish
Location 🧑🏽‍🌾 Seville 💃 Andalusia, UTC+2 🇪🇺
commented
Status: Reviewed & tested by the community » Fixed

Committed af3ce03 and pushed to 8.x-2.x. Thanks!

Status: Fixed » Closed (fixed)

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