#104379Translating content elements in free mode works not correcly
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.
Related issues 1
Files 2
History 5
-
Georg Ringer changed Related to #86738 <span data-processor="relativetime" data-value="2024-07-12T16:11:43+00:00" > 07/12/24, 16:11 </span>
-
Marc Hirdes changed attached mixed_mode.mp4 <span data-processor="relativetime" data-value="2024-08-06T09:02:26+00:00" > 08/06/24, 09:02 </span>
-
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>
-
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.
-
Garvin Hicking commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-08-10T12:52:33+00:00" > 08/10/26, 12:52 </span>Thanks, closing as suggested :)
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:
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.