Issue Bug Closed

#110497TCEFORM sys_language_uid.disabled = 1 doesn't write correct defaults into translated entries breaking loading of IRRE for child elements

Johannes Rebhan 08/18/26, 12:09 updated 10/23/26, 05:41

Description

Since version 14.3.6 (.5 it still works) loading of IRRE elements, that were created with TCEFORM.<model-table>.sys_language_uid.disabled = 1 doesn’t work anymore, since sys_language_uid was stored with 0 in the database, even though the parent object sys_language_uid was for example 3.</model-table>

If the field is not hidden, the GUI will default the field value to the same as the parent element.

We think that hiding fields with disabled = 1 should preserve the behaviour of the GUI defaults and write 3 into the DB. This bug entry is kind of “twofold” in that it is debatable if the old loading behaviour is more robust and should be recovered or if only the GUI default for disabled = 1 should be taken into the future.

Reviews 3

History 1718

  1. Johannes Rebhan commented <span data-processor="relativetime" data-value="2026-08-18T12:25:13+00:00" > 08/18/26, 12:25 </span>

    For any dev stumbling over this. This query would fix the values in the DB, so content is again shown.

    UPDATE <IRRE-element-table>
    SET     sys_language_uid = (SELECT sys_language_uid
                               FROM   <IRRE-parent-table>
                               WHERE  <IRRE-element-parent>.uid =
                                      <IRRE-element-table>.<reference-field>)
    WHERE  <reference-field> IN (SELECT uid
                    FROM   <IRRE-element-table>)

    The where condition is a safeguard against SQL error from orphaned IRRE elements

  2. Johannes Rebhan commented <span data-processor="relativetime" data-value="2026-08-19T13:44:28+00:00" > 08/19/26, 13:44 </span>

    Further information for a testcase: It seems to be connected with “loose” non-base-language objects. If an object is translated from a base-language object, the hidden sys_language_uid has no outcome on the sys_language_uid value in the DB. Only if the non-base-language object is without parent will the sys_language_uid end up being 0 and as a result the fix introduced to Extbase in .6 will correctly filter out those IRRE elements.

  3. Eric Harrer commented <span data-processor="relativetime" data-value="2026-08-28T17:47:41+00:00" > 08/28/26, 17:47 </span>

    We investigated this in the TYPO3 Translation Handling Initiative and documented our current findings in the meeting notes under Topic 3: New Inline Child Language Inheritance.

    The underlying problem appears to be on the write side. FormEngine can initialize the language of a new inline child from its parent. However, if the language field is not submitted, for example because it is disabled via TCEFORM, this value never reaches DataHandler. DataHandler can then fall back to the default permitted language, resulting in sys_language_uid = 0 instead of the language already determined from the parent.

    This is closely related to the historical parent/child language handling discussed in #60026, #76048 and #101962.

    #110498 appears to expose the same underlying problem specifically for newly created sys_file_reference records.

    We currently have a first DataHandler implementation which, for a new inline/file child without an explicitly submitted language, derives the language from its parent. An explicitly submitted child language always takes precedence, so deliberately mixed-language parent/child relations remain possible. Existing child records are not re-languaged.

    The implementation still needs final cleanup, detailed test review and practical before/after verification before being uploaded as WIP.

  4. Benni Mack commented and changed status Under Review Closed <span data-processor="relativetime" data-value="2026-10-23T05:10:24+00:00" > 10/23/26, 05:10 </span>

    Fixed by https://review.typo3.org/c/Packages/TYPO3.CMS/+/87595 (main) and https://review.typo3.org/c/Packages/TYPO3.CMS/+/96783 (14.3): DataHandler now aligns new inline/file children with the language of their parent, also when no language value is submitted (TCEFORM disabled, not in showitem). Verified with the test scenarios of https://review.typo3.org/c/Packages/TYPO3.CMS/+/95476 on current main, so that change is abandoned. Existing wrong rows are not corrected automatically; re-saving the parent aligns its children.

  5. Benni Mack commented <span data-processor="relativetime" data-value="2026-10-23T05:41:58+00:00" > 10/23/26, 05:41 </span>

    Fixed in TYPO3 14.3.10 (and main) by https://review.typo3.org/c/Packages/TYPO3.CMS/+/96783 / https://review.typo3.org/c/Packages/TYPO3.CMS/+/87595: DataHandler now aligns new inline/file children with the language of their parent, also when the language field is not submitted (TCEFORM disabled, not in showitem). The stricter Extbase reading from 14.3.6 is correct and stays; it only exposed records that were stored wrongly. Existing children with a wrong language are not corrected automatically. Note for the SQL above: the safeguard has to check the parent table: <reference-field> IN (SELECT uid FROM <irre-parent-table>).</irre-parent-table></reference-field>