#110498sys_file_reference value of sys_language_uid is assigned with a value of 0 in a translated model if the referenced sys_file has been used by a base language object
Description
Due to changes in how child elements of a translated Model object are loaded (sys_language_uid is now strictly respected) we’ve stumbled across a bug in creating sys_file_references in GUI.
1. Create an Extbase A data entry in base language
2. Reference an image in sys_file
3. Create an additional Extbase B model in a non-base language, without connecting it to a base language object
4. Assign the same sys_file to the B object that was used in A and save
5. Observe the resulting sys_file_reference value of sys_language_uid is 0 instead of the correct sys_language_uid of the Extbase parent object B
Reviews 3
Related issues 12
- Bug #71596New Inline records can not be created in translated parent record
- Bug #76048IRRE: Child records - New record doesn't get language of parent (non localized records but using new button)
- Bug #81165Creating IRRE record within a non-default language record sets wrong sys_language_uid
- Bug #84998sys_language uid isn't updated when parent records sys_languge_uid changes
- Bug #88886DataMapper: Consider languageOverlayMode "hideNonTranslated" when getting relations using consistentTranslationOverlayHandling
- Bug #88980Translating records with FAL relation where allowLanguageSynchronization set to true
- Bug #89787Copying element with IRRE element from one language to another
- Bug #89965Copied textmedia element with sys_file_reference that has its language changed, makes the Datahandler throw up
- Bug #97178Translation of a record with FAL relation not possible after language change from "-1 all" to "0 default"
- Bug #103969Update language of inline elements is missing, leading to follow up issues
- Bug #103970Inline relations do not set the actual language
- Bug #110497TCEFORM sys_language_uid.disabled = 1 doesn't write correct defaults into translated entries breaking loading of IRRE for child elements
History 1516
-
Johannes Rebhan commented <span data-processor="relativetime" data-value="2026-08-19T13:53:49+00:00" > 08/19/26, 13:53 </span>
-
Johannes Rebhan commented <span data-processor="relativetime" data-value="2026-08-19T13:59:17+00:00" > 08/19/26, 13:59 </span>
Another hint: It only seems to affect images added when creating the object. If you later, after having created and saved the object, edit the image and use one that has been used in a base language object elsewhere, it will work. So something is happening when creating objects, that breaks the connect to images in translated, non-connected loose non-base language objects
-
Eric Harrer changed Related to #110497 <span data-processor="relativetime" data-value="2026-08-28T16:26:20+00:00" > 08/28/26, 16:26 </span>
-
Eric Harrer changed Related to #88886 <span data-processor="relativetime" data-value="2026-08-28T16:36:21+00:00" > 08/28/26, 16:36 </span>
-
Eric Harrer changed Related to #76048 <span data-processor="relativetime" data-value="2026-08-28T17:29:58+00:00" > 08/28/26, 17:29 </span>
-
Eric Harrer changed Related to #71596 <span data-processor="relativetime" data-value="2026-08-28T17:31:54+00:00" > 08/28/26, 17:31 </span>
-
Eric Harrer commented <span data-processor="relativetime" data-value="2026-08-28T17:49:31+00:00" > 08/28/26, 17:49 </span>
We investigated this in the TYPO3 Translation Handling Initiative together with #110497 and documented our current findings in the meeting notes under Topic 3: New Inline Child Language Inheritance.
The incorrect
sys_file_reference.sys_language_uid = 0appears to be the same write-side problem described in #110497: if no explicit language is submitted for a newly created child, DataHandler may fall back to language0instead of deriving the language from its parent.The reason this becomes visible with TYPO3 14.3.6 appears to be related to #88886 /
[BUGFIX] Respect language overlay type in Extbase. With the stricter language handling on the read side, an incorrectly stored child is no longer effectively masked when its language does not match the current language context.Our current assumption is therefore that TYPO3 14.3.6 exposes an existing data-creation issue rather than introducing the incorrect
sys_language_uiditself.This also matches the historical parent/child and FAL language handling discussed in #76048 and #71596.
We currently have a first DataHandler implementation which derives the parent language for a new inline/file child only when no language was explicitly submitted. An explicitly chosen child language continues to take precedence.
The implementation still needs final cleanup, detailed test review and practical verification of the TYPO3 14.3.5/14.3.6 behavior before being uploaded as WIP.
-
Gerrit Code Review pushed patch set 1 for main to change 95476 status
NewUnder Review <span data-processor="relativetime" data-value="2026-08-28T21:29:46+00:00" > 08/28/26, 21:29 </span> -
Benni Mack commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-10-23T05:10:34+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.
-
Benni Mack changed Related to #103970 <span data-processor="relativetime" data-value="2026-10-23T05:10:53+00:00" > 10/23/26, 05:10 </span>
-
Benni Mack changed Related to #103969 <span data-processor="relativetime" data-value="2026-10-23T05:11:01+00:00" > 10/23/26, 05:11 </span>
-
Benni Mack changed Related to #81165 <span data-processor="relativetime" data-value="2026-10-23T05:11:28+00:00" > 10/23/26, 05:11 </span>
-
Benni Mack changed Related to #88980 <span data-processor="relativetime" data-value="2026-10-23T05:11:55+00:00" > 10/23/26, 05:11 </span>
-
Benni Mack changed Related to #97178 Related to #84998 <span data-processor="relativetime" data-value="2026-10-23T05:12:22+00:00" > 10/23/26, 05:12 </span>
-
Benni Mack changed Related to #89787 <span data-processor="relativetime" data-value="2026-10-23T05:12:36+00:00" > 10/23/26, 05:12 </span>
-
Benni Mack changed Related to #89965 <span data-processor="relativetime" data-value="2026-10-23T05:13:10+00:00" > 10/23/26, 05:13 </span>
Additional info: if you use the image in a translated object first, then in another base-language object, it works. Only if the image has been used in a base-language object first will this break.
Another hint: it works in ContentBlocks, just not in Extbase