- Issue created by @tlo405
Hey all, just posting again here. I've been considering deleting all paragraphs (and nodes of the node type that uses them) and re-importing after I switch from the 'Paragraphs (stable)' widget to the 'Paragraphs Legacy Asymmetric' widget. However that is slightly risky...if there is a good reason for those duplicates I mentioned above to exist (perhaps something with revisions), I will keep using the 'stale' widget.
I have a block on my site that was using an entity query to get these paragraphs...however that query was returning the duplicates. I was able to work around that problem.... but I just don't think those duplicates should exist at all.
- 🇹🇼Taiwan peterwcm
The Paragraphs Legacy Asymmetric widget changes the original language and removes other translations after creating a duplicate of paragraphs. However, the same logic is not found in the hook_entity_translation_create hook, which is used by the Paragraphs (stable) widget. I have copied the same logic to the hook, which seems to remove the redundant data created during the paragraph clone.
Does anyone know why the logic is not added, I wonder if it's on purpose or a mistake.
- Status changed to Needs review
9 months ago 7:37am 15 August 2024 - 🇨🇭Switzerland idflood
It seems to be related to 🐛 Content moderation workflow changes against one language affect translations too Needs work
So after switching my fields to the Paragraphs Legacy Asymmetric widget, it fixed the related issue. Ssaving a draft in a translation created a new revision in the original language, based on the last published version (ignoring more recent drafts in that language).
@peterwcm thanks a lot for the workaround. I didn't test the patch yet, but the "workaround" gave me back a more stable paragraphs : )