#102345Copy/Move pages with existing translation into another site with different language setup results in orphaned problematic page translation records
Description
Problem/Description
Steps to reproduce
- set up a TYPO3 instance with 2 TYPO3 site configs with different language setup
- site a: default:en (0) + translation:de (1)
- site b: default:de (0) + translation:en (2)
- Create a subpage in site a and add a translation
- Copy the created subpage into site b
- The translated page translation is now “somehow” orphaned as you can only reach it (in TYPO3 12) via the Backend Live Search component (e.g. via
#page:uidOfTranslationor the title)
Resulting problems
- the editor does not know what’s going on
- the editor maybe thinks, that TYPO3 is dumb due to the fact, that the copied records are not changed (default to translation and vice-versa)
- or the editor get’s not stopped by TYPO3 while trying to copy/move a record to another TYPO3 site with a different language setup
- there are scenarios if there are relations like FAL and/or CEs which results in datalost if the orphaned translation get’s deleted via the TYPO3 backend AKA DataHandler
- we also had wrong/problematic speaking urls / slugs. (but this is something I did not investigated when the problem occurs a year ago)
Notes
- in our scenario the problem seems to be occured in TYPO3 9 or 10 when an editor copied a subpagetree from one site to another site. In our scenario, those orphaned page translation records where easily findable via
SELECT uid, pid, sys_language_uid, l10n_source, l10n_parent, slug, title, hidden,cruser_id, deleted FROM pages WHERE deleted = 0 AND l10n_parent != l10n_source; - in 2022, @benni had also the same scenario in his real life projects in B13
- we try to disable copying/moving from one site to another site in this project with hooking into the DataHandler (I will add the workaround code when done/finished)
ToDo(s)
IDK so far.
- stop copy/move from one site to another site via DataHandler when die language setup is not the same betwwen sites
- add a modal with a wizard where the editor have the possibilities to decide what to do
- or introduce a completely new way of copying empty structures. e.g. one wants to copy just the skeleton of a page with empty elements but with correct settings for backendLayout and so… (you see: beLayout can also be differently configured in another site, so one might say just stop copying from site to site :-) )
Acceptance Criteria
- prohibit problematic copy/move or improve this as a feature in the TYPO3 core (TBD)
- document the actual problem until it get’s fixed (or not fixed)
—-
Related external links
- somehow related as it’s actually possible to create translation duplicates for records other then page records:
Reviews 1
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch
- Commit message
-
[BUGFIX] Copy/Move pages with existing translation into another site with different language setup results in orphaned problematic page translation records Resolves: #102345 Releases: main
Related issues 8
- Bug #90610Copy-pasting a record that's already translated in "connected" mode, to a different language causing "free" mode, creates duplicate(s) in "connected" translations
- Bug #93744Copying pages with translations to sites without translations should not copy translations
- Story #101564User Interface related translation issues
- Task #103525Sorting of translated content elements after copy&paste and with no page translation
- Task #103814Add tests for copying localized content to non-translated page
- Bug #103828Copy-Paste: Prevent orphaned
- Bug #104010Copy & Paste creates invisible translations
- Bug #109627Moving content with translation(s) to a free-mode target language leaves orphaned translations
History 1825
-
Josef Glatz changed category Complexity hard <span data-processor="relativetime" data-value="2023-11-07T18:52:26+00:00" > 11/07/23, 18:52 </span>
-
Josef Glatz changed description <span data-processor="relativetime" data-value="2023-11-07T18:53:52+00:00" > 11/07/23, 18:53 </span>
-
Josef Glatz changed category <span data-processor="relativetime" data-value="2023-11-07T18:54:13+00:00" > 11/07/23, 18:54 </span>
-
Josef Glatz changed description <span data-processor="relativetime" data-value="2023-11-07T18:54:47+00:00" > 11/07/23, 18:54 </span>
-
Josef Glatz changed description <span data-processor="relativetime" data-value="2023-11-07T19:01:04+00:00" > 11/07/23, 19:01 </span>
-
Josef Glatz changed category <span data-processor="relativetime" data-value="2023-11-08T06:10:38+00:00" > 11/08/23, 06:10 </span>
-
Josef Glatz changed description <span data-processor="relativetime" data-value="2023-11-08T06:13:05+00:00" > 11/08/23, 06:13 </span>
-
Josef Glatz changed description <span data-processor="relativetime" data-value="2023-11-08T12:34:39+00:00" > 11/08/23, 12:34 </span>
-
Jo Hasenau changed Related to #101564 <span data-processor="relativetime" data-value="2023-11-08T12:34:55+00:00" > 11/08/23, 12:34 </span>
-
André Buchmann commented and changed attached clipboard-202403081039-hvvqf.png attached clipboard-202403081041-gki6w.png attached clipboard-202403081043-ibuah.png <span data-processor="relativetime" data-value="2024-03-08T09:44:01+00:00" > 03/08/24, 09:44 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 83310 status
NewUnder Review <span data-processor="relativetime" data-value="2024-03-08T10:05:15+00:00" > 03/08/24, 10:05 </span> -
Gerrit Code Review pushed patch set 4 for main to change 83310 <span data-processor="relativetime" data-value="2024-03-20T16:13:14+00:00" > 03/20/24, 16:13 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 83310 <span data-processor="relativetime" data-value="2024-04-28T11:05:28+00:00" > 04/28/24, 11:05 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 83310 <span data-processor="relativetime" data-value="2024-04-28T12:22:04+00:00" > 04/28/24, 12:22 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 83310 <span data-processor="relativetime" data-value="2024-04-28T18:39:35+00:00" > 04/28/24, 18:39 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 83310 <span data-processor="relativetime" data-value="2024-04-29T07:34:29+00:00" > 04/29/24, 07:34 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 83310 <span data-processor="relativetime" data-value="2024-04-29T08:36:34+00:00" > 04/29/24, 08:36 </span>
-
André Buchmann changed Related to #103814 <span data-processor="relativetime" data-value="2024-05-10T10:39:54+00:00" > 05/10/24, 10:39 </span>
-
André Buchmann changed Related to #103828 <span data-processor="relativetime" data-value="2024-05-14T08:11:12+00:00" > 05/14/24, 08:11 </span>
-
André Buchmann changed Related to #93744 <span data-processor="relativetime" data-value="2024-06-10T08:45:07+00:00" > 06/10/24, 08:45 </span>
-
Lukas Fürderer changed Related to #104010 <span data-processor="relativetime" data-value="2024-06-10T09:37:33+00:00" > 06/10/24, 09:37 </span>
-
Riccardo De Contardi changed Related to #90610 <span data-processor="relativetime" data-value="2024-06-10T09:40:15+00:00" > 06/10/24, 09:40 </span>
-
Benni Mack changed Related to #103525 <span data-processor="relativetime" data-value="2025-04-12T14:51:58+00:00" > 04/12/25, 14:51 </span>
-
Josef Glatz changed description <span data-processor="relativetime" data-value="2026-03-23T11:36:37+00:00" > 03/23/26, 11:36 </span>
-
Eric Harrer changed Related to #109627 <span data-processor="relativetime" data-value="2026-04-17T11:25:06+00:00" > 04/17/26, 11:25 </span>
I’ve got the same Issue in a real live project with TYPO3 11.5
That’s part of our SiteConfiguration where “global” is the main Site and has the most content. Editors sometimes copy parts of this tree to another site an then replaces the text with the target language. As most trees do only have a single language and the global has 3 translations, there are many orphan/dangling records…
clipboard-202403081039-hvvqf.png
clipboard-202403081041-gki6w.png
It even can result in errors when editors (non-admin) edit the orginial records. The error is caused due to the editor not having access to the other site, but the datahandler tries to update those orphan records also.
clipboard-202403081043-ibuah.png
See also the Slack discussion: https://typo3.slack.com/archives/C05D7UF1L8M/p1709044815292889