Closed djavco closed 2 years ago
Apologies for posting this, I've just read the roadmap, where it says Location rules are totally broken, however I'm not sure the proposed solution would totally fix the above requirement for additive filters and filtering by template.
I can see now if I set 'Manually Set GraphQL Types for Field Group' and then choose 'Page' and the relevant Template in the checkboxes below that the graphql is correctly exposed.
We are working with Gatsby 4, with gatsby-source-wordpress.
If a custom field has a Location rule that is additive i.e 'Post type = page' AND 'Something else = XXX' or 'Post Template = XXX' then gatsby graphql for this custom field is not being exposed.
I can see the graphql in the WordPress GraphiQL IDE on the dashboard but not in the Gatsby ___graphql
We are using: WPGraphQL for Advanced Custom Fields 0.6.1 "gatsby-source-wordpress": "^6.24.0",