-
Notifications
You must be signed in to change notification settings - Fork 63
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
Content is not being saved #787
Labels
Comments
Whoops, looks like I'd forgotten to namespace new blocks when we lazy load the block type's field layout HTML. Thanks for reporting the bug, that's fixed now in 3.9.2. |
There might still be an issue. Vizy won't initialize: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
There seems to be an issue with Neo 3.9.0 and up.
Content is not being saved, sometimes it'll work on the second attempt. Fields are not being initialized, blocks are being removed when saving, etc. Visually, it also seems to refresh when adding a new block.
I've tested and recorded this with parent and child blocks. And with plain text, asset, Vizy (named "rich text" in my test), and Hyper fields. Also tested it with Craft's Entries field, so it might be an issue for all added fields to Neo blocks.
https://share.cleanshot.com/6pyBfWq50BHKrBQFnv5l
Everything works perfectly fine when downgrading to 3.8.6.
This was originally opened at Hyper but it seems to be an issue with Neo instead:
verbb/hyper#90
Steps to reproduce
Expected behaviour
No response
Neo version
3.9.1
Craft CMS version
4.5.5
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
The text was updated successfully, but these errors were encountered: