Problem/Motivation

The settings form is currently not translatable.

Proposed resolution

Add the necessary configuration to allow the settings to be translated. A patch is attached which does this, and changes the help text field to a textarea to assist in translating it through the translation form.

Data model changes

This modifies the configuration schema to set 3 fields (emails and help text) as translatable.

Release notes snippet

Make relevant settings transltable.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dennis_meuwissen created an issue. See original summary.

jcnventura’s picture

Status: Active » Needs work

Please don't change help_text to be a textarea.

dennis_meuwissen’s picture

A new patch is attached. It also seems I forgot to add the tfa.config_translation.yml file last time around.

The help_text type is now changed into a label because leaving it as string and merely adding translatable: true does not make it show up in the translation UI. The config schema docs say type: label is shorthand for type: string, translatable: true though, but that does not seem to work.

jcnventura’s picture

Status: Needs work » Needs review
askibinski’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
1.27 KB
832 bytes

Here is a minor improvement on the patch. The "translatable" property is not necessary because the core mail data type already uses "label" which is translatable by default.

Otherwise tested and works as expected.

  • askibinski authored 2cde671 on 8.x-1.x
    Issue #3156039 by dennis_meuwissen, askibinski, jcnventura: Make...
jcnventura’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for the review and patch. I don't normally accept self-added RTBCs, but in this case I'll give it a pass since you only reduced changes from the original.

Status: Fixed » Closed (fixed)

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