#91465Translated childs wont be marked as deleted in foreign language
Description
Assuming you have a translated content element in LIVE-mode with a parent -> child structure as follows:
parent
– child 1
– child 2
– child 3
The content element was translated in “linked-mode” before.
You delete child 2 in the default language in a workspace.
Expected:- child 2 will be marked as deleted in the default and the foreign language in the workspace
- both deletions can be published in one go.
- child 2 will be marked as deleted only in the default language
- after publishing the change in the default language, child 2 will be marked as deleted in other languages
- this change must be published separately
Poblem with that:
The additional steps are confusing to the users. Editor and publisher are not the same person which can cause some trouble in the publishing workflow which ends up in chaos of content elements.
Reviews 1
Related issues 1
History 2
-
Benni Mack changed Related to #106631 <span data-processor="relativetime" data-value="2026-11-15T14:23:19+00:00" > 11/15/26, 14:23 </span>
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-15T14:24:22+00:00" > 11/15/26, 14:24 </span>
I checked this against the current main branch: the problem no longer exists there.
Cause (v10 – v12)
The child usually already has a workspace version when it is deleted, because the parent was edited in the workspace or the child was modified before. In that case
DataHandlerHook::processCmdmap_deleteAction()turned the version into a delete placeholder and then calledbc. $dataHandler->deleteL10nOverlayRecords($table, $id);
with
$idbeing the uid of the workspace version. Translations point theirl18n_parentto the live uid, so they were not found and not marked as deleted. They only got deleted after the default language record had been published, which then needed a second publish.Fixed by
DataHandler::deleteAction()now looks up the translations by the live uid and turns them into delete placeholders in the same workspace.Verification
A functional test on main with the scenario from this issue: parent content with hotel children, translated in live; then hotel 2 is deleted in a workspace, in three variants (unmodified child, modified child by live uid, modified child by version uid). In all three variants the translated child gets a delete placeholder in the same workspace, so both deletions can be published at once. With the old call (workspace uid) put back, the two “modified child” variants fail.
I am closing this issue as resolved by #106631.