#106658Deleting page translations wrongfully deletes original content elements in default language
Description
Observation:
When a page translation record is deleted, and then the soft-deleted record in the Recycler module
is also completely deleted, the original content elements in the default language are also deleted
completely (removed from the database).
Expected result:
- Only the translated page and it’s translated content elements should be deleted
- The original content elements in the default language should not be deleted
Steps to reproduce:
- Create a new page
- Add content elements to the page in the default language
- Translate the page
- Translating the content elements is optional. It happens with and without translated content elements. The translation mode (“connected” or “copy”) doesn’t matter either
- Delete the page translation, not the translated content elements. The translated content elements will be deleted automatically
- Go to the Recycle module and delete all soft-deleted records
- Go back to the newly createad page from step 1
- The content elements in the default language are completey deleted
Reviews 2
Related issues 1
History 69
-
Rony Khoury commented <span data-processor="relativetime" data-value="2025-05-07T08:46:52+00:00" > 05/07/25, 08:46 </span>
As discussed in the TYPO3 slack channel (typo3-cms-coredev), I’ve tried to reproduce the issue.
I’ve created two fresh installations with the versions
13.4.9and13.4.8without installing any extra extensions.For reproducibility, I’ve followed install instructions for DDEV: [[https://get.typo3.org/version/13#version-download]]
For the
13.4.8installation, in thecomposer.jsonfile I changed all version numbers from"^13.4"to the fix version"13.4.8".Results:
- In the
13.4.9instance, the same issue occurred as described in this bug report. - In the
13.4.8instance, the issue didn’t occur. Only the translated page was deleted.
- In the
-
Christian Kuhn changed Related to #106382 <span data-processor="relativetime" data-value="2025-05-07T10:56:03+00:00" > 05/07/25, 10:56 </span>
-
Christian Kuhn commented <span data-processor="relativetime" data-value="2025-05-07T11:07:29+00:00" > 05/07/25, 11:07 </span>
Thank you! Great analysis. git bisect says this was introduced with #106382, which was a hairy but rather important change. I’ll see what I can do to fix the situation.
-
Gerrit Code Review pushed patch set 1 for main to change 89314 status
NewUnder Review <span data-processor="relativetime" data-value="2025-05-07T12:15:01+00:00" > 05/07/25, 12:15 </span> -
Gerrit Code Review pushed patch set 2 for main to change 89314 <span data-processor="relativetime" data-value="2025-05-07T13:05:13+00:00" > 05/07/25, 13:05 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 89316 <span data-processor="relativetime" data-value="2025-05-08T08:55:21+00:00" > 05/08/25, 08:55 </span>
-
Christian Kuhn commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-05-08T09:05:09+00:00" > 05/08/25, 09:05 </span>Applied in changeset commit:435b39efb45b7c7f57956f52d4d7631769992963.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:21:22+00:00" > 12/02/25, 14:21 </span>
Some details of my setup I forgot to add to the ticket description: