Problem/Motivation

Steps to reproduce

1. Create any node and translate that node.
2. Now delete translated node.
3. you can check original language node got deleted

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#3 3325939-original-language-node-got-deleted-on-delete-of-translated-node.patch886 bytesthi3rry

Comments

Yatendra Singh created an issue. See original summary.

hchonov’s picture

hchonov
Primary language Bulgarian
Location Burgas
commented
Status: Active » Postponed (maintainer needs more info)

How is the conflict module supposed to prevent this normal Drupal behavior?

thi3rry’s picture

thi3rry commented
Related issues: +#2491057: Streamline the entity deletion form class hierarchy
StatusFileSize
new 3325939-original-language-node-got-deleted-on-delete-of-translated-node.patch886 bytes

I can confirm the issue on drupal 9.5.0.

The NodeDeleteForm extends the ContentEntityDeleteForm that implements EntityFormInterface, but in fact the NodeDeleteForm is here to delete the node or a translation of the node.

There is currently a work in progress on this : https://www.drupal.org/node/2491057
I don't know where the conflict module conflict with that drupal behavior.

We are using the attached patch to restore the drupal core behavior by removing the conflict_prepare_entity_form() on ContentEntityDeleteForm instance.

akalam’s picture

akalam commented

I can confirm the issue on Drupal 9.4.x, the issue is indeed related with ContentEntityDeleteForm is being responsible of deleting the entity. Skiping the alter for delete forms as in #3 seems like a solution and fixed the issue for me.