You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that Neo isn't saving changes to my field layout. I can remove a field from a block's layout and if I hit the save button and then go back to the same block, the field I removed is still there even though the notification says the field changes were saved.
Steps to reproduce
Remove a field from a block's field layout.
Save the field.
Check the block type again after saving and the field you removed is still there.
Expected behaviour
No response
Neo version
4.0.8
Craft CMS version
4.8.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:
Removing a field from a block type's field layout is working as expected for me. If possible, could you please send your composer files and database backup to plugins@spicyweb.com.au and let us know which Neo field and block type this is happening with, and we'll have a look.
Thanks for sending those files. That block type and a few others shared the same field layout, which is puzzling and a little concerning. I have added a console command for the next release (php craft neo/block-types/fix-field-layouts) to duplicate the field layout so each block type gets its own version. If you'd like to apply that fix before the next release, set your composer.json file's spicyweb/craft-neo requirement to 4.x-dev as 4.0.8 and run composer update.
Bug Description
I noticed that Neo isn't saving changes to my field layout. I can remove a field from a block's layout and if I hit the save button and then go back to the same block, the field I removed is still there even though the notification says the field changes were saved.
Steps to reproduce
Expected behaviour
No response
Neo version
4.0.8
Craft CMS version
4.8.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: