Issue Bug Under Review Stale

#110328Transl.Orig selector offers records already translated into the target language

Eric Harrer 07/30/26, 09:23 updated 07/31/26, 22:58

Description

Problem

When editing a connected translation of a content element, the Transl.Orig [l18n_parent] selector offers default-language records that are already used as the translation parent of another active record in the same target language.

Assigning such a record and saving the form creates multiple translated content elements with the same combination of:

  • target language (sys_language_uid)
  • translation parent (l18n_parent)

The regular record-editing workflow therefore allows an inconsistent localization state to be created.

This inconsistency also causes different backend modules to resolve and display different translations for the same default-language content element.

Prerequisites

  • TYPO3 v14 or TYPO3 15.0.0-dev
  • A site with a default language and at least one additional language
  • A page translated into the additional language
  • Two content elements in the default language

Steps to reproduce

  1. Create two default-language content elements, referred to as content element 1 and content element 2.
  2. Use the translation wizard in Content > Layout to create connected translations of both records in the same target language.
  3. Open the translated record of content element 2.
  4. Open the Language tab.
  5. Change Transl.Orig from content element 2 to content element 1, although content element 1 is already assigned as the translation parent of the translated content element 1.
  6. Save the record.
  7. Compare the translated page in the Page module and the List module.

Actual behavior

The record is saved successfully.

Both translated records now have the same target language and reference content element 1 through tt_content.l18n_parent.

The Transl.Orig selector neither prevents the duplicate assignment nor indicates that content element 1 is already used by another active translation in the current target language.

The resulting inconsistent state is handled differently by backend modules:

  • The Page module only displays the translated content element 2.
  • The List module only displays the translated content element 1.

A video demonstrating the complete workflow and the differing results in both modules is attached.

Expected behavior

The Transl.Orig selector must not offer a default-language record that is already assigned as the translation parent of another active record in the current target language.

The following records must remain selectable:

  • The translation parent currently assigned to the edited record
  • Default-language records that do not yet have an active connected translation in the current target language

The regular record-editing workflow must not allow multiple active records to acquire the same combination of target language and translation parent.

The Page and List modules must consequently operate on an unambiguous translation relation and display the same connected translation.

Reproducibility

  • Reproducible: Yes
  • Initially observed: Translation Handling Initiative meeting on 2026-07-24
  • Confirmed affected versions: TYPO3 v14 and TYPO3 15.0.0-dev
  • Earlier versions: Not verified
  • Regression: Not verified

Technical analysis

For tt_content, the TCA transOrigPointerField is configured as l18n_parent.

For connected translations, the combination of the target language and the translation parent is expected to identify a single active translated record. The record-editing form currently does not enforce this invariant when manually changing l18n_parent.

Filtering the Transl.Orig selector should therefore account for:

  • the target language of the record being edited
  • existing active translations using each possible parent
  • the UID of the record currently being edited, so that its existing parent remains selectable
  • applicable enable fields and record-state restrictions

The inconsistent Page- and List-module results indicate that different record-retrieval paths resolve the ambiguous translation relation differently. Preventing the duplicate assignment would avoid creating this ambiguous data state through the regular editing workflow.

Scope

  • In scope: Preventing duplicate translation-parent assignments through the regular record-editing form
  • In scope: Filtering default-language records that are already used by another active translation in the current target language
  • In scope: Preserving the current record’s existing parent as a selectable option
  • Out of scope: Repairing existing inconsistent database records
  • Out of scope: Restoring deleted records
  • Out of scope: Conflicts introduced through Workspace publication

Additional information

Forge #97094 covers an incorrect translation status after manually changing Transl.Orig. It does not request that already occupied translation parents be excluded from the selector.

Forge #107071 describes the same duplicate target-language and translation-parent data structure being created through Workspace publication. The issue described here concerns the regular record-editing workflow.

Reviews 1

History 34

  1. Eric Harrer commented <span data-processor="relativetime" data-value="2026-07-31T20:57:07+00:00" > 07/31/26, 20:57 </span>

    The Translation Handling Initiative discussed this issue again during its meeting on 2026-07-31 and refined the expected scope and filtering rules.

    The solution should not be limited to tt_content.l18n_parent. It should apply generically to every translatable table through the field configured as ctrl.transOrigPointerField.

    For the record currently being edited, the selector should:

    • offer records from the same table and page,
    • offer only records from the default language or “all languages” records using sys_language_uid IN (0, -1),
    • exclude potential translation parents that are already referenced by another non-deleted translation in the current target language,
    • retain the translation parent currently assigned to the edited record.

    An additional compatibility rule is required for record types.

    If the table defines a TCA type field and that field is configured with l10n_mode = exclude, only potential parents whose type value matches that of the current translated record should be selectable.

    Without this restriction, assigning a parent with a different type can cause the translated record to inherit that type and unexpectedly change its complete editing form.

    This equality requirement should deliberately not be generalized to every field using l10n_mode = exclude. Differences in fields such as colPos can be intentional, while synchronized fields on tables such as pages or sys_file_metadata are not necessarily structural prerequisites for selecting a translation parent. Fields using allowLanguageSynchronization should also remain outside the initial scope because their synchronization remains under editorial control.

    The selector is currently generated by TcaEnrichment, which enriches the configured transOrigPointerField as a selectSingle field. A possible implementation direction would be to replace the generic foreign_table selection with a dedicated typed itemsProcessor that retrieves only eligible translation-parent records according to the rules above.