Issue Bug Closed

#108771Form element properties cannot be overridden via YAML when generic XLF translation exists

Ioulia Kondratovitch 01/26/26, 08:46 updated 03/03/26, 16:07

Description

Component

  • Form Framework (EXT:form)

TYPO3 versions

  • 12.4.40
  • 13.4.24

Summary

The documentation states that certain form element properties are “Overwritable within form definition: Yes” . However, when rendering forms in frontend (Fluid), if a generic XLF translation key exists in core’s locallang.xlf , the YAML property value is ignored. The XLF translation always takes precedence, making YAML overrides impossible for these properties.

Affected properties

3 properties in core are affected:

_.Element _.Property _.Core XLF Key _.Default Value
DatePicker timeSelectorHourLabel element.DatePicker.properties.timeSelectorHourLabel “Hour”
DatePicker timeSelectorMinuteLabel element.DatePicker.properties.timeSelectorMinuteLabel “Minute”
ImageUpload SummaryPage.altText element.ImageUpload.properties.SummaryPage.altText “Uploaded image”

Steps to reproduce

1. Create a form definition YAML with all 3 affected properties and summary step (see 00_Test-YAML-Property-Override-vs-XLF.form.yaml attached):

type: Form
identifier: testYamlPropertyOverrideVsXlf
label: '00_Test: YAML Property Override vs XLF'
prototypeName: standard
renderables:
  - type: Page
    identifier: page-1
    label: 'Test Page'
    renderables:
      - type: DatePicker
        identifier: datepicker-1
        label: 'Date Picker'
        properties:
          displayTimeSelector: true
          elementDescription: 'Custom description'
          timeSelectorHourLabel: 'Custom Hour Label'
          timeSelectorMinuteLabel: 'Custom Minute Label'
      - type: ImageUpload
        identifier: imageupload-1
        label: 'Image Upload'
        properties:
          saveToFileMount: '1:/user_upload/'
          allowedMimeTypes:
            - image/jpeg
            - image/png
          SummaryPage.altText: 'Custom Alt Text for Summary'
  - type: SummaryPage
    identifier: summary-1
    label: 'Summary'

Note: Use flat dot notation for SummaryPage.altText , not nested structure. TranslateElementPropertyViewHelper wraps property string as single-element array, not split by dots.

2. Render the form in frontend, upload an image, proceed to summary page
3. Check time selector labels and alt attribute in HTML source for summary page image

Expected result

  • elementDescription : “Custom description” (visible)
  • timeSelectorHourLabel : “Custom Hour Label” (visible)
  • timeSelectorMinuteLabel : “Custom Minute Label” (visible)
  • SummaryPage.altText : “Custom Alt Text for Summary” (in HTML source)

Actual result

  • elementDescription : “Custom description” (visible) ✅ no generic XLF key exists
  • timeSelectorHourLabel : “Hour” (visible) ❌ from XLF, YAML ignored
  • timeSelectorMinuteLabel : “Minute” (visible) ❌ from XLF, YAML ignored
  • SummaryPage.altText : “Uploaded image” (in HTML source) ❌ from XLF, YAML ignored

Root cause

Current fallback chain

The current implementation in TYPO3\CMS\Form\Service\TranslationService::translateFormElementValue() uses this priority:

1. XLF: .element.{elementIdentifier}.properties.{property} (form + element specific)
2. XLF: element.{elementIdentifier}.properties.{property} (element specific)
3. XLF: element.{elementType}.properties.{property} (generic element type) ← **blocks YAML**
4. YAML: properties.{property} (only if no XLF found)

Expected fallback chain

Swap steps 3 and 4:

1. XLF: .element.{elementIdentifier}.properties.{property} (form + element specific)
2. XLF: element.{elementIdentifier}.properties.{property} (element specific)
3. YAML: properties.{property} ← was 4
4. XLF: element.{elementType}.properties.{property} (generic fallback) ← was 3

Note: This is already the effective behavior for properties without generic XLF keys (like elementDescription ).

Code reference

TranslationService::translateFormElementValue() – 3 locations where generic element-type key is added:
  • options property handling
  • fluidAdditionalAttributes property handling
  • general property handling (else block)

The YAML property ( $defaultValue ) is only used when no translation is found. Since core’s locallang.xlf defines generic keys like element.DatePicker.properties.timeSelectorHourLabel , the YAML value is never used.

Suggested fix

Change priority order to match “Expected fallback chain” above.

Documentation reference

https://docs.typo3.org/c/typo3/cms-form/13.4/en-us/I/Config/proto/formElements/formElementTypes/DatePicker.html#properties-timeselectorhourlabel

States:
> “Overwritable within form definition: Yes”

—-

Related issues

1. Documentation gap

SummaryPage.altText property missing from: https://docs.typo3.org/c/typo3/cms-form/13.4/en-us/I/Config/proto/formElements/formElementTypes/ImageUpload.html

2. SummaryPage.html template bug

The SummaryPage.html templates (both v1 and v2) use wrong property path for ImageUpload :

_.File _.Current _.Should Be
Frontend/Partials/SummaryPage.html property: ‘altText’ property: ‘SummaryPage.altText`
FrontendVersion2/Partials/SummaryPage.html property: ‘altText’ property: ‘SummaryPage.altText’

3. FormEditor HMAC bug

SummaryPage.altText is not in FormEditor property whitelist ( ImageUpload.yaml ). Forms containing this property cannot be saved in backend – HMAC validation fails even when editing unrelated fields:

503 Oops, an error occurred!
Exception while property mapping at property path "": No hmac found for property "properties.SummaryPage.altText" (form element "imageupload-1") #1528588037

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.