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'm trying out this plugin and have a page with a complex field for sections. One of the sections is a gallery which is a complex field itself with a variable number of images in it. The setup looks like this:
Everything works using the REST API and with GraphQL if I remove the gallery section so I suspect the problem is with the nested complex fields. Have I done something obviously wrong? Has anyone run into something similar?
Update: so it seems the nested complex fields work as long as I do not add any other type of section. So on a page with only galleries, the query works, but if I add a prose section the query immediately fails, even if I don't include the content field in the query.
Update 2: I get the same issue when I use the built in media_gallery field type. Works fine by itself, but adding another type of field causes the error.
The text was updated successfully, but these errors were encountered:
I'm trying out this plugin and have a page with a complex field for sections. One of the sections is a gallery which is a complex field itself with a variable number of images in it. The setup looks like this:
and a query like this:
And I get this error in the response:
Everything works using the REST API and with GraphQL if I remove the
gallery
section so I suspect the problem is with the nested complex fields. Have I done something obviously wrong? Has anyone run into something similar?Update: so it seems the nested complex fields work as long as I do not add any other type of section. So on a page with only galleries, the query works, but if I add a
prose
section the query immediately fails, even if I don't include thecontent
field in the query.Update 2: I get the same issue when I use the built in
media_gallery
field type. Works fine by itself, but adding another type of field causes the error.The text was updated successfully, but these errors were encountered: