Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.4.13]: Cli command 'craft resave/entries' make neo blocks loose their nesting #13256

Closed
Tim-Wils opened this issue May 26, 2023 · 4 comments
Closed

Comments

@Tim-Wils
Copy link

What happened?

Description

We're busy with a Craft 3 to 4 update for our client.
Almost everything went really smooth, until we arrived at the point where we had to resave all the entries.

Doing php craft resave/entries affects entries neo blocks tomake them loose their nesting.

Steps to reproduce

  1. Do php craft resave/entries and all the blocks loose their nesting.

Screen before:
image

Screen after doing: php craft resave/entries --element-id 25867
image

Craft CMS version

Craft Pro 4.4.13

PHP version

8.1.3

Operating system and version

Linux 5.15.90.1-microsoft-standard-WSL2

Database type and version

MariaDB 10.2.44

Image driver and version

No response

Installed plugins and versions

Neo is on dev-main with this fix from Brandon Kelly to try and if this will fix it, but it doesn't: spicywebau/craft-neo@7232a30

@i-just
Copy link
Contributor

i-just commented May 26, 2023

Hi, thanks for reaching out. I'm having trouble replicating this issue. Any chance you can send your composer.json, composer.lock and database export from before you run the resave command to support@craftcms.com so that we can dig deeper?

@i-just
Copy link
Contributor

i-just commented May 30, 2023

@Tim-Wils, thanks for sending over the files. I’ve narrowed it down to a conjunction of Preparse Field and Neo. I’ll update again once I know more.

@Tim-Wils
Copy link
Author

Tim-Wils commented Jun 1, 2023

@i-just Removing Preparse completely solves the problem. So Preparse definitely is the culprit. Luckily, the field wasn't needed in this project anymore. Thank you for helping out!

@i-just
Copy link
Contributor

i-just commented Jun 1, 2023

Not a problem at all. Glad you managed to make it work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants