[5.x]: Duplicated Nested Entries

[ryanleichty]

What happened?

Description

We've noticed nested entries being randomly duplicated a few times now. I'm not quite sure what's causing it—whether it's an authoring issue with copying elements or something draft related—but figured I would report it in case other's are experiencing this too. We'll keep an eye out in case it happens again and we can pinpoint what's causing it.

We're using nested entries in a page builder like experience and authors are creating drafts on the root owner entry.

Steps to reproduce

1. It seems to be draft related, though I haven't been able to recreate the issue manually yet.

Expected behavior

No duplicated nested entries

Actual behavior

Craft CMS version

5.8.14

PHP version

8.2.26

Operating system and version

Linux 5.10.238-234.956.amzn2.x86_64

Database type and version

MySQL 8.0.40

Image driver and version

Imagick 3.7.0 (ImageMagick 7.1.1-32)

Installed plugins and versions

Alt Text Generator 5.2.1
Amazon S3 2.2.3
Asset Usage 4.1.3
CKEditor 4.10.0
Colour Swatches 5.1.0
Empty Coalesce 5.0.0
Hyper 2.2.7
Image Hotspots 3.0.1
Neo 5.4.5
Retcon 3.2.1
Retour 5.0.11
SEOmatic 5.1.16
Template Selector 5.0.1

[linear]

CMS-1541 [5.x]: Duplicated Nested Entries

[ryanleichty]

This just happened again on another page. It definitely seems draft related. Not sure if it has anything to do with the part where it merges updates to the current revision into the draft?

We’re still having issues come up when we do homepage drafts. I’ll attach some screenshots, but I have checked this draft more than once and when I logged in today, it brought back the previous hero with the new hero we want to use. I then deleted that hero option and when I “applied the draft” that old hero came back in again! I did hit ‘discard’ changes at the top but I don’t think we want to continue doing that everytime?
For now though, we should be good with a push the site this mornning to launch the Acrylic Prints sale today. Thanks!

Here’s showing the double heroes when I opened the draft this morning

I then deleted the one hero and then hit applied draft and got this, showing that hero is back again:

[Thijmen]

We've seen this on Craft 4 as well, but never bothered to create an issue for it because it was impossible to reproduce. Our case was also in non-draft cases.

[Thijmen]

We have multi site, perhaps that also matters.

[brandonkelly]

@ryanleichty Any chance you can share a database backup and your Composer files with us? We can try to reproduce with that. support@craftcms.com

[ryanleichty]

@brandonkelly Awesome! Just sent an email with the backup. Is it just the composer.json file that's needed?

[brandonkelly]

Both composer.json and composer.lock preferably

[Thijmen]

@brandonkelly any update on this matter? No rush ofcourse - but it's occasionally happening at our Craft install too. Can't pin-point the exact use-case though... I wonder also what the best way to "target" the use-case... storing all POST data somewhere would seem like we need a lot of data to store...

[brandonkelly]

@Thijmen Looks like we haven’t gotten anywhere with @ryanleichty’s files (and in a holding pattern waiting for additional info).

If you’re able to come up with steps to reproduce, please let us know the details!