-
Notifications
You must be signed in to change notification settings - Fork 122
ACF Options fields null in Schema after latest update (v0.5.0) #254
Comments
Can confirm this is also happening to me too as per discussion on wpgraphql slack https://wp-graphql.slack.com/archives/C5X592Z99/p1619145882096700 This is how I'm registering the options page
And my field group json
|
I experienced the same problem, and think I may have found the issue. After adding That parameter seems to be defining how data is returned from options pages here: wp-graphql-acf/src/class-config.php Line 412 in c2120f6
IMO should either the logic be updated or the "type" requirement be added to the docs. |
@lindvall thanks for the added context here. I'll look into this and see if we can resolve it, either in code or in documentation. |
Hi, same problem here |
👋🏻 Hey! Apologies for this regression! I've got this fixed (and tested properly) in #257. Will get this released shortly! |
…null #254 - add back missing type declaration for options pages.
This has been released as v0.5.2 https://github.com/wp-graphql/wp-graphql-acf/releases/tag/v0.5.2 |
So excited about the new location rules changes, but I think this may be a new bug.
I have an Options page in Wordpress, provided custom fields by ACF. These fields were previously shown in the GraphQL schema.
After updating to version 0.5.0, those fields now show as 'null' instead of their actual value in the schema.
I can't seem to find a way around this.
The text was updated successfully, but these errors were encountered: