Wrong order of neo fields when using richtext (ckeditor) with nested entries

[Jones-S]

Bug Description

We use Neo fields to create a Page Builder where editors can put together different content blocks. We do this for years now but recently we detected a very weird behaviour: When adding a new Richtext Block (ckeditor) and if we nest an entry (Button) inside, this blocks is now returned as the first item of the array instead of the last.

To better understand I have created this short screen recording:
https://www.dropbox.com/scl/fi/yl81jao9u9g175q6chakx/Craft-Richtex.mov?rlkey=ge0b87tvpb4q552e0gjbewcw0&e=1&st=v72wkzpg&dl=0

I first escalated this to the Craft team and they pointed me to neo. They were also able to reproduce.

This is at the moment kind of a critical bug for us and for one of our clients, as they can't really fill in the content, if the position is always changing and not corresponding to what the editor says.

Thank you in advance.

Steps to reproduce

Please contact me via PM and I am glad to share you a zip file with a DB dump, composer json and the templates for reproduction.

Expected behaviour

The new neo block should be at the end corresponding to the content editors position.

Neo version

5.2.21

Craft CMS version

Craft Pro 5.5.7

What is the affected Neo field's propagation method?

No response

Does this issue involve templating, and if so, is eager-loading used?

This is not a templating issue

[ttempleton]

If you're unable to reproduce this with CKEditor fields nested in inline-editable Matrix blocks, could you please send your database backup, composer files and a minimal template reproduction to plugins@spicyweb.com.au and we'll have a look.

[Jones-S]

Did you receive my email? Unfortunately our client is kind of pushing the issue drastically 😅...

[ttempleton]

Thanks for sending that through @Jones-S. Unfortunately the templates sent through aren't sufficient for a reproduction (i.e. showing the blocks in order in some form). The entry shown in the video also doesn't exist in the provided database, which I'm guessing is part of a removal of non-shareable data before sending the database - this is fine, of course, but we would still need to be able to reproduce the issue on a remaining entry.

Using the following template code:

<ul>
    {% for block in entry.pageBuilder.level(1).all() %}
        <li>{{ block.id }}; {{ block.type.handle }}</li>
    {% endfor %}
</ul>

and following the steps from the video using the homepage entry, the blocks appeared in the correct order on the preview frame.

If these are the same files that were sent to the Craft team, could you please let us know (through email if you prefer) an alternative entry in the database backup that we could use to reproduce the issue?

[Jones-S]

Ah well I should have mentioned that we use it headless and just get the content via GraphQL. I just forwarded you my email exchange which I had with Craft cms support, and they were able to reproduce from that linked zip file (which should be the same I sent to you).

So regarding the templates: I think you should just be able to query via GraphQL. And then the order in the PageBuilder array should be wrong.
For further help I attached an example queries:
Just make sure to import the pageBuilder fragments.

graphql.zip

[ttempleton]

Thanks for that @Jones-S - that's now fixed for the next release. In the meantime, you can get the fix by setting your composer.json file's spicyweb/craft-neo requirement to 5.x-dev as 5.2.21 and running composer update.

[Jones-S]

Thank you for the quick fix. So far it's looking good!

[ttempleton]

Just released 5.2.22 including this fix.