Closed nedu64 closed 5 days ago
If possible, could you please send your composer.json/lock files and database backup to plugins@spicyweb.com.au, along with directions to an entry where this reliably happens, and we'll have a look.
Thanks for looking into this @ttempleton. We won't be able to send a copy of the database for the install that we're seeing this issue on. However, we're going to test with version 4.2.7 of Neo, and if the issue we're seeing is still present, we'll set up a fresh Craft install and try and reproduce it - we would then be able to send you a copy of that DB.
If possible, could you please send your composer.json/lock files and database backup to plugins@spicyweb.com.au, along with directions to an entry where this reliably happens, and we'll have a look.
@ttempleton Done, also note that the issue is also reproducible in version 4.2.8
Thanks for that @nedu64 - fixed now in 4.2.9.
Bug Description
I currently have a Neo field which contains a few blocks used in adding various content to a page. Based on the Block configuration and the issue at hand, i noticed adding child blocks to an existing child block up to level 4 seems a bit problematic when querying its modified Drafts content as tested using Graphiql playground. Here is a bit of description of the block configuration:
Pictorial Description
Adding content to any of the Hidden Content's Block works in Live Preview when saved. However if you create a Draft from the saved page and make any modifications to any of the Hidden Content's Child Blocks, Graphiql playground returns an empty response for the Child Blocks: E.g:
Saved content below
Query (Graphiql):
Response:
Accordion item
block e.g:Response:
Steps to reproduce
Expected behaviour
Adding changes to a nested block up to Level 4 in a created Draft, i'm able to see these changes when querying using Craft's Graphiql Playground
Neo version
4.1.2
Craft CMS version
Craft Pro 4.9.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