#109627Moving content with translation(s) to a free-mode target language leaves orphaned translations
Description
Description
When a default-language tt_content record that already has translations is moved into a non-default target language that is handled in free mode, TYPO3 can leave existing translations behind in an invalid state.
In the observed scenario, the moved record changes its sys_language_uid to the non-default target language, while existing translations remain unchanged in the database. Their l18n_parent relation then no longer points to a default-language record, so they become orphaned translation records. In addition, these orphaned records are no longer visible in the Layout module.
The move operation must not silently create this inconsistent state.
Steps to reproduce
- Create a default-language
tt_contentrecord. - Create at least one existing translation of that record.
- Ensure that the target language is handled in free mode.
- Move the default-language record into that non-default target language using the backend page module workflow.
- Inspect the remaining translations in the backend and in the database.
Actual behavior
- The moved record receives the target
sys_language_uid. - Existing translations remain in the database.
- Their
l18n_parentrelation is no longer valid because it no longer points to a default-language record. - The remaining translation records become orphaned and are no longer visible in the Layout module.
Expected behavior
- The move operation must not silently create orphaned translation records.
- TYPO3 should either block the move or require an explicit destructive confirmation before proceeding.
- If the destructive path is chosen, TYPO3 should handle the affected translations explicitly and consistently, for example by soft-deleting them and informing the editor.
- If the editor does not confirm, the move must be cancelled.
Impact / rationale
The current behavior compromises data consistency and can hide affected records from editors while keeping them in the database.
A silent orphaning of translation records is not acceptable. At the same time, a destructive cleanup without explicit confirmation would also be too risky.
Related issues / patches
- #108358 / 93063 is related but narrower: it focuses on a warning for already orphaned content elements in a specific constellation. The scope of this report is the move operation itself and the requirement that TYPO3 must not silently create orphaned translation records.
- #102345 is broader historical context around orphaned translation records during problematic copy/move operations across different language setups, but it is primarily page-focused and does not cover this exact
tt_contentmove-to-free-mode scenario.
Reviews 1
Related issues 2
History 46
-
Eric Harrer changed Related to #108358 Related to #102345 <span data-processor="relativetime" data-value="2026-04-17T11:25:06+00:00" > 04/17/26, 11:25 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:51+00:00" > 04/21/26, 11:23 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 93819 status
NewUnder Review <span data-processor="relativetime" data-value="2026-04-23T08:55:55+00:00" > 04/23/26, 08:55 </span> -
Eric Harrer commented and changed attached MoveTranslatedContentToFreeModeLanguagePatchset1.mp4 <span data-processor="relativetime" data-value="2026-04-23T09:23:34+00:00" > 04/23/26, 09:23 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 93819 <span data-processor="relativetime" data-value="2026-04-23T09:46:15+00:00" > 04/23/26, 09:46 </span>
-
Eric Harrer changed target version TYPO3 Version
1415 <span data-processor="relativetime" data-value="2026-04-24T06:23:04+00:00" > 04/24/26, 06:23 </span>
The attached video demonstrates the following use cases based on the current patch set: