Issue Bug Under Review Orphaned

#109627Moving content with translation(s) to a free-mode target language leaves orphaned translations

Eric Harrer 04/17/26, 11:24 updated 04/24/26, 06:23

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

  1. Create a default-language tt_content record.
  2. Create at least one existing translation of that record.
  3. Ensure that the target language is handled in free mode.
  4. Move the default-language record into that non-default target language using the backend page module workflow.
  5. 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_parent relation 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_content move-to-free-mode scenario.

Reviews 1

History 46

  1. 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>

    The attached video demonstrates the following use cases based on the current patch set:

    • Drag & drop translated content to first/last position in default language
    • Drag & drop translated content to free language + cancel
    • Drag & drop translated content to free language + confirm “Move Record” dialog
    • Drag & drop non-default language content (with l18n_parent=0) back to default language
    • Drag & drop untranslated content to free language (no dialog)
    • Cut & paste translated content to first/last position in default language
    • Cut & paste translated content to free language + cancel
    • Cut & paste translated content to free language + confirm “Move Record” dialog
    • Cut & paste non-default language content (with l18n_parent=0) back to default language
    • Cut & paste untranslated content to free language (no dialog)