Issue Bug Under Review

#106915Localized records disappear after editing and moving them in WS

Amir Arends 06/19/25, 13:07 updated 11/19/26, 05:18

Description

Steps to reproduce:

  • Switch to a Workspace.
  • Open the List module.
  • Edit a localized record (either a page or tt_content – the issue occurs with both).
  • Move the localized record down.
  • The localized item becomes invisible in the list view.

Cause:

During the DataHandler datamap (for editing items) processing, the localized record is saved in the workspace with an incorrect transOrigPointerField (e.g., l10n_parent). It references the live record with sys_language_uid = 0, which causes it to disappear in the workspace context. In contrast, cmdmap (for moving items) processing saves the localized record correctly by referencing the workspace version of the original record with sys_language_uid = 0.

This leads to inconsistent behavior and missing localized records in the backend when working in a workspace.

Reviews 7

History 718

  1. Christian Kuhn commented <span data-processor="relativetime" data-value="2025-06-23T12:38:35+00:00" > 06/23/25, 12:38 </span>

    More detailed reproduce:

    • Create a page in live
    • Add two content elements (“ce1” and “ce2”).
    • Localize page
    • Localize the two content elements (“translate”, not “copy”)
    • Go to workspaces
    • Change the localized (!) “ce1” (e.g. “header field) in workspaces
      - A ws-overlay t3ver_state 0 (“changed”) is created, l18n_parent points to the default-language LIVE (!) record since there is no default-language overlay of that record in workspaces.
    • Resort the default language “ce1” below “ce2” using page module drag&drop or list module sorting buttons.
      - A ws-overlay t3ver_state 4 (“moved”) is created, and the previously created ws-overlay of the localization is changed from t3ver_state 0 to 4. The localization now does have a default language parent record in workspaces, but l18n_parent is NOT updated to this uid.
      - from default language workspace point of view, the localization is now “lost” in page and list module.

    Note: When not moving, but changing the default language record in workspaces, after a localization has been changed, this results in the same DB state that l18n_parent is not updated of the localized record. However, both page and list module still show the localized record.

    Question: should we update the l10n_parent uid of the localized record in such situation? imho yes, but we will have to check what happens with l18n_parent when later only the localized record is published.
    Question: what is the result in FE in both scenarios?

  2. Markus Klein commented <span data-processor="relativetime" data-value="2026-03-19T14:23:36+00:00" > 03/19/26, 14:23 </span>

    Minimal reproducer:

    • Have a page with at least 1 additional translation
    • Switch to workspace
    • Move that page. Lets say a notch to the bottom
    • Click the view-button of the translation

    Result:

    Slider for “published” shows correct content,
    Slider for “staged” shows no content

  3. Philipp Kitzberger commented <span data-processor="relativetime" data-value="2026-04-22T12:38:41+00:00" > 04/22/26, 12:38 </span>

    Don’t know if that’s the same issue: but when moving tt_content in v13 workspaces the result is a bit different:

    • the FE preview via slider view works fine (for both live and staged)
    • the BE edit mask shows MISSING LABEL for field `l18n_parent` (it points correctly to the workspace’d version of the translation origin though, but the dropdown only contains the live records)

    After publishing, all’s fine again.