Issue Bug Under Review

#107108behaviour::AllowLanguageSynchronization works badly in FlexForm

Davide Alghi 07/17/25, 10:57 updated 11/18/26, 20:50

Description

  1. all fields in flexform have got the same name (HTML attribute “name”), so the “Translation Behavior” radio buttons (Custom value, Value of default language) don’t work
  2. the default value becomes a xml file content if “Value of default language” option is selected
  3. the delete button (the “x” of input box on right side) is always active, also when “Value of default language” option is selected

flex field TCA:

        'simple_field' => [
            'exclude' => false,
            'label' => 'Simple Field',
            'description' => 'A simple field to test allowLanguageSynchronization in FlexForm',
            'config' => [
                'type' => 'flex',
                'ds' => [
                    'default' => 'FILE:EXT:test1752731870/Configuration/FlexForms/SimpleField.xml',
                ],
                'behaviour' => [
                    'allowLanguageSynchronization' => true,
                ],
            ],
        ],

NB: the same in T3-13 (not tested in T3-12)

attached a video to reproduce the issue
attached the ext for testing

.

Reviews 1

Files 2

History 12

  1. Eric Thibault commented <span data-processor="relativetime" data-value="2025-12-19T20:16:29+00:00" > 12/19/25, 20:16 </span>

    We are experiencing the same issue in TYPO3 versions 12 and 13 (not tested in 11).

    This bug is problematic for us because we have upgraded form TYPO3 version 10. So, our content editors added a lot of resources in our alternate language and, after upgrading to TYPO3 12, informed us that they were losing resources!

    After investigation, we have noticed that the new feature “Translation behavior” was set to “value of default language” even when custom resources were present in the alternate language before the upgrade! The resources were visually lost after saving while editing in both the main and alternate language without any error message.

    We have found that we had “Array” in the l10n_state field of table pages for pages that have lost resources in the alternate language after saving… working perfectly in TYPO3 10.

    We have also found that the “visually lost” resources were present in the table sys_file_reference but “deleted”. Undeleting them manually in the database brought them back after saving with “Custom values” for the “Translation behavior”.

    To reproduce the bug:
    1. Add an alternate language if not present;
    2. Create a new page;
    3. Add an image resource in the alternate language;
    4. save;
    5. Success message in shown;
    6. Alternate language resources tab only shows the main language image if one existed;
    7. The “sys_file_reference” contains the lost image resource that was added in the alternate language;

    Minimally, the migration documentation should mention that, with secondary languages, we should be careful and manually change the “Translation behavior” to “Custom value” before saving in TYPO3 version 12 and up.

    Deactivate all UI controls that are set to use “Value of default language” for “Translation behavior”… at this moment, only controls for creating or editing relations are still active. I could be also interesting that TYPO3 detects when custom resources are present in the alternate language and automaticaly switches to “Custom value”!

    Thank you for your time!