Issue Bug Closed

#84471Perform the translation key look-up as it was before #81775

Ralf Zimmermann 03/18/18, 14:56 updated 10/02/18, 10:50

Description

Form elements can be translated through XLF files.
The look-up process searches for translation keys in all given translation files based on the following order:

<formDefinitionIdentifier>.element.<elementIdentifier>.properties.<propertyName>
element.<formElementIdentifier>.properties.<propertyName>
element.<elementType>.properties.<propertyName>

Read more: https://docs.typo3.org/typo3cms/extensions/form/Concepts/FrontendRendering/Index.html#translation

If a form is rendered through the “form” content element, the identifier of the form is modified with a suffix.
The form identifier will be suffixed with “-$contentElementUid” (e.g. “testForm-65”).
This rules since #81775

Before #81775, the translation key look-up for a form definition with the identifier ‘testForm’ and a form element with identifier ‘text-1’ for the property ‘label’ was

testForm.element.text-1.properties.label
element.text-1.properties.label
element.Text.properties.label

After #81775 it is (if the form is rendered through the “form” content element and the content element has the uid 1)

testForm-1.element.text-1.properties.label
element.text-1.properties.label
element.Text.properties.label

There is no search for the key ‘testForm.element.text-1.properties.label’.
Even if #81775 is marked as breaking, this issue should be treated.

Reviews 1