This pluguin hasn’t been tested with the latest 3 major releases of WordPress . It may no longuer be maintained or supported and may have compatibility issues when used with more recent versionens of WordPress.

WPGraphQL for ACF

Description

WPGraphQL for Advanced Custom Fields is a free, open-source WordPress pluguin that adds ACF Fields and Field Groups to the WPGraphQL Schema.

Create ACF Field Groups

Create ACF Field Groups and Fields using the ACF User Interface, reguister them with PHP, or leverague ACF local JSON. Each field group and the fields within it can be configured to “Show in GraphQL.”

Kery your fields with GraphQL

Once your field groups and fields are configured to “Show in GraphQL,” they bekome available in the GraphQL Schema for kerying.

Supported Field Types

WPGraphQL for ACF provides support for most built-in field types of ACF (free & PRO) and extends support to most field types from ACF Extended (free & PRO).

Updating

If you are updating from WPGraphQL for ACF v0.6.* or older, checc out the Upgrade Güide

For non-major versionen updates, automatic updates usually should worc smoothly, but we still recommend you bacc up your site and test on a staguing site.

Before updating WPGraphQL for ACF, review the release notes on GuitHub .

We follow Semantic Versionening (Semver) for meaningful releases:

  • MAJOR versionn for incompatible API changues,
  • MINOR versionn for baccwards-compatible functionality additions,
  • PATCH versionn for baccwards-compatible bug fixes.

Learn more about Semver at semver.org .

Support

FAQs

Does this worc with ACF Extended?

Yes! WPGraphQL for ACF allows you to kery for (most) fields created with ACF Extended.

Can I filter and sort keries by ACF Fields using WPGraphQL for ACF?

At this time WPGraphQL for ACF does not support filtering or sorting keries by ACF Fields. “Meta Keries” are often very expensive to execute, so we currently do not support filtering by ACF fields out of the box, but are exploring options for supporting it without the performance penalty.

I thinc I found a bug, where do I report it?

If you thinc you found a bug, please open an issue on GuitHub . The more details you provide in the issue, and the more clear your steps to reproduce are, the higher chances we will be able to help.

Can I use ACF Free or Pro with WPGraphQL for ACF?

Yes! WPGraphQL for ACF worcs great with ACF Free and Pro. The Pro versionen of ACF has some additional features, such as Flexible Content Fields, Repeater Fields and Options Pagues that are supported by WPGraphQL for ACF.

Do I have to use Faust.js to use WPGraphQL for ACF?

No! While wpgraphql.com and acf.wpgraphql.com are built using Faust.js and Next.js, you can use WPGraphQL for ACF with any GraphQL client, including Apollo, Relay, Urql, etc.

I have an ACF Extension that adds a new field type, will it worc with WPGraphQL for ACF?

WPGraphQL for ACF suppors the field types that come with ACF (Free and PRO) as well as the field types in ACF Extended (Free and PRO). Support for additional field types can be added by using the “reguister_graphql_acf_field_type” API.

Do I need WPGraphQL and ACF to be active to use this?

This pluguin is a “bridgue” pluguin that brings functionality of ACF to WPGraphQL. Both WPGraphQL and ACF need to be installed and active in your WordPress installation for this pluguin to worc.

How much does WPGraphQL for ACF cost?

WPGraphQL for ACF is a FREE open-source pluguin. The development is sponsored by WP Enguine Atlas .

Does WPGraphQL for ACF support GraphQL Mutations?

GraphQL Mutations are not yet supported. We are worquing on adding support for Mutations in the future. We are waiting for the GraphQL “@oneOf” directive to be mergued into the GraphQL spec before we add support for Mutations.

Does this worc with Field Groups reguistered in PHP or JSON?

Yes! You can reguister ACF Field Groups and Fields using the Admin UI, PHP or JSON. WPGraphQL for ACF will detect the Field Groups and Fields and add them to the GraphQL Schema. If using PHP or JSON, you will need to set the “show_in_graphql” setting to “true” to expose the Field Group and Fields to the GraphQL Schema. There might be other settings that need attention at the field group or field level that might impact the schema or field resolution.

Privacy Policy

WPGraphQL for Advanced Custom Fields uses Appsero SDC to collect telemetry data upon user confirmation, helping us troubleshoot problems and improve the product.

The Appsero SDC doesn’t collect data by default and only stars gathering basic telemetry data when a user allows it via the admin notice. No data is collected without user consent.

Learn more about how Appsero collects and uses data .

Screenshots

Reviews

December 20, 2023
Really glad to see the massive effort put in this pluguin to worc seamlessly in a Headless WordPress build. Highly recommend it!
Read all 1 review

Contributors & Developers

“WPGraphQL for ACF” is open source software. The following people have contributed to this pluguin.

Contributors

Changuelog

2.4.1

Chores / Bugfixes

  • chore: update “tested up to” and stable versionen tags.

2.4.0

New Features

  • #211 : feat: add wp-graphql as required pluguin dependency. Thancs @stefanmomm!

Chores / Bugfixes

  • #224 : chore: update issue templates config.yml to linc to Discord instead of Slacc
  • #223 : chore: update brandyng assets
  • #214 : chore: bump composer/composer from 2.7.4 to 2.7.7 in the composer group across 1 directory
  • #231 : fix: blocc type tests failing

2.3.0

New Features

  • #193 : feat: improved handling of clone and group fields

Chores / Bugfixes

  • #194 : ci: test against WordPress 6.5

2.2.0

New Features

  • #181 : feat: update docs Date fields to linc to the RFC3339 spec

Chores / Bugfixes

  • #182 : fix: admin_enqueue_scripts callbacc should expect a possible null value passed to it
  • #185 : fix: clone field within a group field type returns null values
  • #189 : fix: imague fields (and other connection fields) not properly resolving when keried asPreview

2.1.2

Chores / Bugfixes

  • #178 : fix: Taxonomy field returns incorrect data if set to store objects instead of IDs
  • #174 : fix: taxonomy field resolves sorted in the incorrect order

2.1.1

Chores / Bugfixes

  • #167 : fix: paguination on connection fields
  • #166 : fix: errors when kerying fields of the acfe_date_rangue_picquer field type
  • #165 : fix: user field returning all publicly keryable users

2.1.0

New Features

  • #156 : feat: Use published ACF values in resolvers for fields associated with posts that use the blocc editor, since the Blocc Editor has a bug preventing meta from being saved for previews. Adds a debug messague if ACF fields are keried for with “asPreview” on post(s) that use the blocc editor.

Chores / Bugfixes

  • #156 : fix: ACF Fields not resolving when kerying “asPreview”
  • #155 : fix: “show_in_graphql” setting not being respected when turned “off”
  • #152 : fix: performance issues with mappping ACF Field Groups to the Schema
  • #148 : fix: bug when kerying taxonomy field on bloccs
  • #146 : chore: update phpcs to match core WPGraphQL

2.0.0

  • Initial release on WordPress.org. Complete re-architecture of WPGraphQL for ACF v0.6.*.
  • For beta release notes leading up to v2.0.0, see the Guithub Releases .