Only core ACF fields are returned
There's loads of extensions available for Advanced Custom Fields. I am not exactly sure how they extend ACF, but I can imagine that there's an API that's being used. this website (https://www.awesomeacf.com) offers up to 170 extensions, also there's the plugin ACF: Extended that implements various new field types. In several projects we use the plugin 'Advanced Custom Fields: Font Awesome Field' to offer users a way to select an icon for various purposes.
At this moment the current implementation of GraphQL for Advanced Custom Fields seems to return the data from core fields but not the data from fields that are added by extensions for ACF. I'm not sure if support for GraphQL is something that plugin developers need to implement themselves, or if ACF offers a way to extend the current output with data from third party fields.
I'm going to transfer this to the WPGraphQL for ACF repo.
WPGraphQL for ACF exposes hooks and filters to allow extensions to add GraphQL support. We're in the progress of some significant changes to the WPGraphQL for ACF plugin, and once we stabilize more, we'll be putting out a comprehensive tutorial/doc on how ACF extensions can play nice with WPGraphQL.
We may add some support for some of the extensions, but it won't scale for us to maintain support for 170 (and growing) extensions. Ideally, with proper docs and community support, some of the extensions can take ownership of their integration with GraphQL.
Stay tuned for more updates in this space in the coming weeks.
Hi @jasonbahl, any news on this? Thanks!
Any updates?
Updates? We are having the same problem with 3rd party FontAwesome acf in graphQL
I'm interested in this as well because I'd like to use this Gravity Forms ACF field type with WPGraphQL.
👋🏻 we're working on a new version of WPGraphQL for ACF over here: https://github.com/wp-graphql/wpgraphql-acf.
The new version has an API for adding support for third party ACF Field Types.
In fact, the plugin comes with support for ACF Extended Field Types and you can use them as a model for adding support for additional ACF Field Types such as the Open Streetmap field type.
For example:
While we won't be supporting all ACF Field Type extensions out of the box, we will be supporting the APIs for developers to add their own custom ACF Field Types more easily.
We'd recommend checking out the new version of WPGraphQL for ACF as it's what we'll be supporting going forward. It will have a stable release on WordPress.org in the near future and this version will be archived.