Issue Bug Closed

#104379Translating content elements in free mode works not correcly

Marc Hirdes 07/12/24, 13:17 updated 08/10/26, 12:52

Description

It’s similar to this issue: https://forge.typo3.org/issues/86738

The workflow is the same.

Create a new content element in the default language in free mode. In this content element select on top the translation option [NEW]. Now the editor is creating a connected element, because the l18n_parent has the uid from the source element.

So the page is now in connected mode… This confuses the editors.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 2

History 5

  1. Eric Harrer commented and changed attached step-based-translation-wizard.mp4 <span data-processor="relativetime" data-value="2026-05-18T09:29:32+00:00" > 05/18/26, 09:29 </span>

    This issue was resolved in TYPO3 v14 by the modernized translation workflow introduced with Feature #108049: Modernized Translation Workflow.

    I tested the described scenario in the backend and recorded the current behavior in the attached video.

    Here is what I observed:

    • If a translation is already being used in free mode, free mode is retained when translating additional content.
    • Similarly, if a translation is already being used in connected mode, connected mode is retained when translating additional content.
    • If no localization mode exists yet because there are no translations at all, the editor can explicitly choose between free mode and connected mode.

    This means that the previously confusing behavior in mixed mode, which was described in this ticket, can no longer occur.

    @mhirdes If you can also confirm that the problem has been resolved, we can close the issue.

  2. Marc Hirdes commented <span data-processor="relativetime" data-value="2026-08-10T11:31:13+00:00" > 08/10/26, 11:31 </span>

    Yes, thanks Eric for your feedback. You can close this issue. I can’t.

  3. Garvin Hicking commented and changed status New Closed <span data-processor="relativetime" data-value="2026-08-10T12:52:33+00:00" > 08/10/26, 12:52 </span>

    Thanks, closing as suggested :)