If I try to add a neo block to a new entry, all matrix fields within that neo block cannot be added unless a draft is saved first. In craft-neo 5.0.1, it was possible to populate matrix fields within neo block without needing to save a draft (unless there was some error in the form). But something changed in later versions. In 5.0.4, it's not possible to populate matrix fields nested within neo block. If it's a required field, there is no way to create an entry without saving a draft first
Once I save a draft, I'm able to create matrix within neo block.
Steps to reproduce
Set autoSaveDrafts to false in CMS config
Create a new entry
Add a neo block that contains a matrix field
The matrix field shows this message "Entries can only be created after the Neo block has been saved."
Expected behaviour
I should be able to create matrix fields within neo blocks without having to save a draft.
Neo version
5.0.4
Craft CMS version
5.2.0
What is the affected Neo field's propagation method?
No response
Does this issue involve templating, and if so, is eager-loading used?
Bug Description
If I try to add a neo block to a new entry, all matrix fields within that neo block cannot be added unless a draft is saved first. In craft-neo 5.0.1, it was possible to populate matrix fields within neo block without needing to save a draft (unless there was some error in the form). But something changed in later versions. In 5.0.4, it's not possible to populate matrix fields nested within neo block. If it's a required field, there is no way to create an entry without saving a draft first![image](https://github.com/spicywebau/craft-neo/assets/1942688/2009ecf1-c859-4760-8847-2708d620c3c3)
Once I save a draft, I'm able to create matrix within neo block.![image](https://github.com/spicywebau/craft-neo/assets/1942688/67acbf76-c756-4d76-858f-53dfd9bb6c01)
Steps to reproduce
autoSaveDrafts
to false in CMS configExpected behaviour
I should be able to create matrix fields within neo blocks without having to save a draft.
Neo version
5.0.4
Craft CMS version
5.2.0
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