WPGraphQL for Advanced Custom Fields

Overview

WPGraphQL for Advanced Custom Fields

WPGraphQL for Advanced Custom Fields automatically exposes your ACF fields to the WPGraphQL Schema.

Install and Activate

WPGraphQL for Advanced Custom Fields is not currently available on the WordPress.org repository, so you must download it from Github, or Composer.

Installing From Github

To install the plugin from Github, you can download the latest release zip file, upload the Zip file to your WordPress install, and activate the plugin.

Click here to learn more about installing WordPress plugins from a Zip file.

Installing from Composer

composer require wp-graphql/wp-graphql-acf

Dependencies

In order to use WPGraphQL for Advanced Custom Fields, you must have WPGraphQL and Advanced Custom Fields (free or pro) installed and activated.

Adding Fields to the WPGraphQL Schema

TL;DR: Here's a video showing an overview of usage.

Advanced Custom Fields, or ACF for short, enables users to add Field Groups, either using a Graphical User Interface, PHP code, or local JSON to various screens in the WordPress dashboard, such as (but not limited to) the Edit Post, Edit User and Edit Term screens.

Whatever method you use to register ACF fields to your WordPress site should work with WPGraphQL for Advanced Custom Fields. For the sake of simplicity, the documentation below will primarily use the Graphic User Interface for examples.

Add ACF Fields to the WPGraphQL Schema

The first step in using Advanced Custom Fields with WPGraphQL is to create an ACF Field Group.

By default, field groups are not exposed to WPGraphQL. You must opt-in to expose your ACF Field Groups and fields to the WPGraphQL Schema as some information managed by your ACF fields may not be intended for exposure in a queryable API like WPGraphQL.

Show in GraphQL Setting

To have your ACF Field Group show in the WPGraphQL Schema, you need to configure the Field Group to "Show in GraphQL".

Using the ACF GUI

When using the ACF Graphic User Interface for creating fields, WPGraphQL for Advanced Custom Fields adds a Show in GraphQL field to Field Groups.

Setting the value of this field to "Yes" will show the field group in the WPGraphQL Schema, if a GraphQL Field Name is also set

Show in GraphQL Setting for ACF Field Groups

Registering Fields in PHP

When registering ACF Fields in PHP, you need to add show_in_graphql and graphql_field_name when defining your field group. See below as an example.

function my_acf_add_local_field_groups() {

	acf_add_local_field_group(array(
		'key' => 'group_1',
        'title' => 'My Group',
        'show_in_graphql' => true,
        'graphql_field_name' => 'myGroup',
		'fields' => array (
			array (
				'key' => 'field_1',
				'label' => 'Sub Title',
				'name' => 'sub_title',
				'type' => 'text',
			)
		),
		'location' => array (
			array (
				array (
					'param' => 'post_type',
					'operator' => '==',
					'value' => 'post',
				),
			),
		),
	));

}

add_action('acf/init', 'my_acf_add_local_field_groups');

Each individual field will inherit its GraphQL name from the supplied name tag. In this example, sub_title will become subTitle when requested through GraphQL. If you want more granular control, you can pass graphql_field_name to each individual field as well.

Supported Fields

In order to document interacting with the fields in GraphQL, an example field group has been created with one field of each type.

To replicate the same field group documented here you can download the example field group and import it into your environment.

For the sake of documentation, this example field group has the location rule set to "Post Type is equal to Post", which will allow for the fields to be entered when creating and editing Posts in the WordPress dashboard, and will expose the fields to the Post type in the WPGraphQL Schema.

Location rule set to Post Type is equal to Post

Options Pages

Reference: https://www.advancedcustomfields.com/add-ons/options-page/

To add an option page and expose it to the graphql schema, simply add 'show_in_graphql' => true when you register an option page.

Example Usage

function register_acf_options_pages() {

    // check function exists
    if ( ! function_exists( 'acf_add_options_page' ) ) {
        return;
    }

    // register options page
    $my_options_page = acf_add_options_page(
        array(
            'page_title'      => __( 'My Options Page' ),
            'menu_title'      => __( 'My Options Page' ),
            'menu_slug'       => 'my-options-page',
            'capability'      => 'edit_posts',
            'show_in_graphql' => true,
        )
    );
}

add_action( 'acf/init', 'register_acf_options_pages' )
Example Query
query GetMyOptionsPage {
    myOptionsPage {
        someCustomField
    }
}

Alternatively, it's you can check the Fields API Reference to learn about exposing your custom fields to the Schema.

Location Rules

Advanced Custom Fields field groups are added to the WordPress dashboard by being assigned "Location Rules".

WPGraphQL for Advanced Custom Fields uses the Location Rules to determine where in the GraphQL Schema the field groups/fields should be added to the Schema.

For example, if a Field Group were assigned to "Post Type is equal to Post", then the field group would show in the WPGraphQL Schema on the Post type, allowing you to query for ACF fields of the Post, anywhere you can interact with the Post type in the Schema.

Supported Locations

@todo: Document supported location rules and how they map from ACF to the WPGraphQL Schema

Why aren't all location rules supported?

You might notice that some location rules don't add fields to the Schema. This is because some location rules are based on context that doesn't exist when the GraphQL Schema is generated.

For example, if you have a location rule to show a field group only on a specific page, how would that be exposed the the Schema? There's no Type in the Schema for just one specific page.

If you're not seeing a field group in the Schema, look at the location rules, and think about how the field group would be added to a Schema that isn't aware of context like which admin page you're on, what category a Post is assigned to, etc.

If you have ideas on how these specific contextual rules should be handled in WPGraphQL, submit an issue so we can consider how to best support it!

Comments
  • Feature Request: Limit field group to a specific page?

    Feature Request: Limit field group to a specific page?

    On many sites we build, we often have many ACF field groups specific to the page you are editing. For example, if it's the "Front page", or a "Contact page", or a top level page of some sort, or if this is a child page. It would be a real bummer if our "Contact" ACF field group has to be on every page.

    I saw in Slack you plan on allowing us to limit field groups to custom templates, but that's not ideal. It will mean having to create a bunch of empty PHP files just for this, and page templates don't work great with custom post types either.

    It seems the limitation is WP GQL not knowing the ID or page name during the query. Is there a better way we could come up with then? Perhaps our own rule set of some other data? A meta field called "Developer ID" perhaps? Or even the URI perhaps?

    Screen Shot 2019-04-25 at 3 56 48 PM

    enhancement 
    opened by drewbaker 26
  • Field groups not in schema when location is a page template

    Field groups not in schema when location is a page template

    When a field group is tied to a page template for its location, it seems as though it is not available to pages in the GraphQL schema. I also tried combining the rules so it's set as page AND page template === whatever but that still didn't work.

    Any possibility of this landing in the future? I did see you can use page === page name as the location but usually we want to tie them to template so either us or a client can create a new page based off of a template without having to change field group settings.

    Needs Discussion Location Rules 
    opened by nathobson 21
  • Relationship field query errors out for anonymous when set to some non-published post

    Relationship field query errors out for anonymous when set to some non-published post

    Say you have a post relationship field called "Related Content" in a Post custom fields group (say "Post Fields"). If a selected post within that field is set to private, draft, or some other state where the anonymous user cannot view it; the query will return an error. I would instead expect the system to simply return null (which it does) and give no errors.

    Example query:

    {
      postBy(postId: 13) {
        status
        title
        postFields {
          relatedContent {
            __typename
            ... on Post {
              id
              title
            }
          }
        }
      }
    }
    

    Result:

    {
      "errors": [
        {
          "message": "Internal server error",
          "category": "internal",
          "locations": [
            {
              "line": 6,
              "column": 7
            }
          ],
          "path": [
            "postBy",
            "postFields",
            "relatedContent",
            0
          ]
        }
      ],
      "data": {
        "postBy": {
          "status": "publish",
          "title": "Some Post",
          "postFields": {
            "relatedContent": [
              null
            ]
          }
        }
      }
    }
    

    Tested on:

    • WordPress 5.2.4
    • Advanced Custom Fields 5.8.6
    • WP GraphQL 0.4.0
    • WPGraphQL for ACF 0.3.0
    :rocket: Actionable effort: low impact: medium Field Type: Relationship 
    opened by mdrayer 18
  • Regression on relationship fields since WPGraphQL 1.7.0

    Regression on relationship fields since WPGraphQL 1.7.0

    Since WPGraphQL 1.7.0 it is not possible to query relationship fields. I can't tell if it's a problem with the connectors or with the new version of GraphiQL

    https://github.com/wp-graphql/wp-graphql/compare/v1.6.12...v1.7.0

    Before

    CleanShot 2022-04-11 at 19 38 48

    After

    CleanShot 2022-04-11 at 19 48 43

    There is no difference between version 1.7.0 after npm i + npm build or version 1.8.0. Works fine until 1.6.12

    ACF 5.9.5 WPGraphQL 1.7.0 - 1.8.0

    opened by rodrigo-arias 14
  • ACF_Link is being registered multiple times

    ACF_Link is being registered multiple times

    In trying to track down why my Gatsby previews are failing, and in the process I noticed a warning stating:

    "type": "DUPLICATE_TYPE",
    "message": "You cannot register duplicate Types to the Schema. The Type 'ACF_Link' already exists in the Schema. Make sure to give new Types a unique name.",
    "type_name": "ACF_Link",
    

    I found where this message is printed out in wp-graphql-1.0/src/Registry/TypeRegistry.php and put an error_log statement in place. My error log got flooded out with this same error about ACF_Link being registered multiple times.

    In looking at wp-graphql-acf-release-v0.3.5/src/class-config.php in the method register_graphql_field, for the case link, it appears to always register the $field_type_name of ACF_Link, whereas other cases in here seem to append other variances to the end of the field name before registering them. When putting error_log() statements in this case I find dozens/hundreds of times ACF_Link gets used for the $field_type_name (even though they each have differing $type_name values).

    I'm not sure if this is related to my preview not working, but I wanted to file a ticket as it seems this warning is firing hundreds of times under the covers either way and potentially should be revisited..?

    Duplicate Fields 
    opened by SmartyP 14
  • Add Explicit options for adding ACF Field Groups to the Schema

    Add Explicit options for adding ACF Field Groups to the Schema

    Currently, the way WPGraphQL for ACF implicitly maps field groups from ACF Location Rules to the WPGraphQL Schema causes a lot of confusion.

    ACF has a lot of location rules that require specific run-time context that's not available for Schema generation.

    For example, rules such as Page is not equal to Home or Post is equal to Hello World don't exactly map well to a Schema.

    The Schema is representative of all Types available, and context such as whether a Page is the Home Page, or a Post is the "Hello World" post is runtime context.

    So, in an effort to reduce this confusion, I'm working on a more explicit setting where you can define the GraphQL Types to show the ACF Field Group on, and not rely on the location rules at all.

    The location rules can be used for determining the editing experience, and the new setting can be used for determining explicitly which Types the field group should be available on in the Schema.

    Something like the following:

    Screen Shot 2020-04-20 at 1 56 00 PM

    This checkbox field will show all Types that can have field groups associated with them. Post Types and Taxonomies that are exposed to GraphQL, Users, Comments, Menus, Menu Items, Media, Page Templates, etc.

    enhancement :rocket: Actionable Breaking Change Component: API 
    opened by jasonbahl 13
  • ACF fields not showing on graphiql console

    ACF fields not showing on graphiql console

    Hello, First of all, thanks for the amazing work you're doing offering theses plugins :)

    I've followed many different videos to set up wp-graphql and add some custom fields including @jasonbahl tutorial on youtube, and everything result the same.

    Wordpress Version: 5.4.1

    After i've added some custom fields through my posts and checked show in in graphql the group and the fields, when i'll query it i just get the possibility to get the "fieldGroupName": "acfDemoFields", but nothing else with my fields.

    List of plugins i've installed : image

    Graphql schema : image

    Graphql query: image

    Custom field group : image

    I really don't have any idea why it doesn't show up Im on linux but i've tried aswell on windows, to see if there is any difference, not at all.

    Thanks for your time

    status: awaiting author response Question 
    opened by DarioRega 13
  • Fatal error on plugin activation

    Fatal error on plugin activation

    Plugin could not be activated because it triggered a fatal error.

    Warning: require({pathto}\wp-content\plugins\wp-graphql-acf\vendor\composer/../phpstan/phpstan/bootstrap.php): failed to open stream: No such file or directory in {pathto}\wp-content\plugins\wp-graphql-acf\vendor\composer\autoload_real.php on line 69

    Fatal error: require(): Failed opening required '{pathto}\wp-content\plugins\wp-graphql-acf\vendor\composer/../phpstan/phpstan/bootstrap.php' (include_path='{pathto}\php\PEAR') in {pathto}\wp-content\plugins\wp-graphql-acf\vendor\composer\autoload_real.php on line 69

    bug status: awaiting author response Needs to be reproduced 
    opened by sulemanhelp 11
  • mediaDetails query error

    mediaDetails query error

    Hi

    I'm not sure if maybe I have some other issue in my setup but the following query produces an error:

    {
      mediaItems {
        nodes {
          mediaDetails {
            sizes {
              mimeType
            }
          }
        }
      }
    }
    
    GraphQL\Error\Error: String cannot represent non scalar value: {"ext":"jpg","type":"image\/jpeg"}
    
    opened by homerjam 11
  • Fix #135. Add Explicit options for adding ACF Field Groups to the Schema

    Fix #135. Add Explicit options for adding ACF Field Groups to the Schema

    This PR focuses on fixing the experience of mapping ACF Field Groups to the WPGraphQL Schema.

    This video walks through the update:

    https://youtu.be/VvrZGrcwv0Y


    closes #135

    opened by rsm0128 10
  • Relationship field crashes when referencing trashed posts as anonymous

    Relationship field crashes when referencing trashed posts as anonymous

    To reproduce

    • Create relationship field to a custom post type (might occur with buildin types too)
    • Create a page with some referenced posts
    • Move one of the referenced post to trash
    • Make an anonymous graphql query listing those posts
    {
      page(idType: URI, id: "/test-page") {
        myFieldGroup {
          contacts {
            ... on Contact {
              title
              uri
            }
          }
        }
      }
    }
    

    Here's the myFieldGroup is an ACF field group and contacts is the custom post type.

    When running this from the graphiql in wp-admin it works but when sending it as an anonymous query it errors with with:

    Abstract type Page_MyFieldGroup_Contacts must resolve to an Object type at runtime for field Page_MyFieldGroup.contacts with value \"instance of WPGraphQL\\Model\\Post\", received \"null\". Either the Page_MyFieldGroup_Contacts type should provide a \"resolveType\" function or each possible type should provide an \"isTypeOf\" function.
    

    My initial investigation leads here:

    https://github.com/wp-graphql/wp-graphql-acf/blob/01577deb0a474f5387d60d3680a69ff810bddf35/src/class-config.php#L520

    The issue goes away if I add $post_object->post_status === 'publish' check for anonymous users before appending to the $relationship array but I'm not sure this is the right place to do it.

    Thoughts?

    I can also provide better reproduce steps with code if needed.

    opened by esamattis 10
  • Custom acf blocks image url not showing

    Custom acf blocks image url not showing

    I have created custom acf blocks other fields render fine but image field rendering values number find image for example

    attributes: data: button: {title: 'DOWNLOAD RESUME', url: 'http://example.com.au/app/uploads/2022/12/SUNIL-SINGH2022.pdf', target: ''}enable_disable_module: "1"heading_1: "SUNIL "heading_2: "SINGH"hero_image: 17sub_heading: "I AM A FULL STACK WEB DEVELOPER"_button: "field_6345f391a8325"_enable_disable_module: "field_6346010b6dd8f"_heading_1: "field_6345ef9305807"_heading_2: "field_6345f52cfbe6e"_hero_image: "field_6345f1ce05809"_sub_heading: "field_6345f1a105808"[[Prototype]]: Objectmode: "edit"name: "acf/hero-module"

    image image

    opened by sunilsingh2019 4
  • No data resolved in page link fields when using internal link

    No data resolved in page link fields when using internal link

    Hi.

    With

    • ACF Pro Version 5.9.5
    • WP GraphQL Version 1.10.0
    • WP GraphQL for ACF Version 0.6.1, previously 0.5.2

    We're seeing an issue where the page link component when using internal links doesn't return anything through GraphQL.

    The value exists in storage, and resolution appears to work in part, but fails halfway through.

    It used to work. In fairness, we have a fairly complex setup, but I tried stripping it down to near-barebones WordPress, and was able to reproduce the issue.

    We're using PHP 7.4.

    opened by maurocolella 1
  • Inputs not showing in mutation on registerUser or createUser

    Inputs not showing in mutation on registerUser or createUser

    Hello, I am using a headless Wordpress with ACF (Version 6.0.3), ACF Extended (Version 0.8.8.10), WP-GraphQL (Version 1.12.0) and WPGraphQL for Advanced Custom Fields (Version 0.5.3) installed.

    In ACF I created a field group with some fields and set the condition to User Role == All. The Goal is to add some fields to the regular WP-User and register a user including those fields.

    When I now want to use the GraphQL-IDE to click together a mutation to register a new user, the ACF fields I created aren't there as inputs. So I can't register a user using those fields. I wonder if I've done anything wrong.

    Under registerUser or createUser I can find a node user and under that I can find the field group I have created. But not as inputs.

    Here are some screenshots: ACF field group

    GraphQL Settings

    GraphQL-IDE Query Composer

    opened by michaelgrossklos 0
  • Feature request: Checkboxes return value and label

    Feature request: Checkboxes return value and label

    This is identical to #44 but checkboxes (or return multiple values).

    checkboxes-return

    Solutions I've tried:

    • The snippet included in #44
    • Modifying above snippet
    • Select field returning multiple selections
    • A select within a repeater

    I feel all options are expecting to return one selection [value, label] instead of multiple{[value, label], [value, label]}

    Happy to privately share an endpoint if necessary πŸ˜„

    Thanks

    opened by aleeceburgess 0
  • Getting url of Image field, when Rules are set to

    Getting url of Image field, when Rules are set to "Show this filed group if [Block] is equal to [My Custom Block]"

    I created a ACF custom block with image field (not for Post in Custom Fields Settings), and in GraphiQL I cannot find the image url...

    ACF field group Screen Shot 2022-09-27 at 1 39 39 PM

    GraphiQL result Screen Shot 2022-09-27 at 1 51 59 PM I only get the image number, not the url... (in this case, 37)

    Is there any way I can get the image url?

    opened by jjung830 1
  • Possible to set graphql_field_name option in GUI?

    Possible to set graphql_field_name option in GUI?

    I have a few of fields which field names start with a number, but this throws an error "The field '1280720' on Type 'Project_Afcprojectsettings_FeaturedGfxList_Src' is invalid. Field names cannot start with a number."

    When registering with php or json I can set graphql_field_name to avoid this error. But cant do this with the admin fields. Could it be added as an option?

    opened by jackgregory 0
Releases(v0.6.1)
  • v0.6.1(Sep 16, 2022)

    What's Changed

    • Revert "filter returned value with acf/format_value" by @jasonbahl in https://github.com/wp-graphql/wp-graphql-acf/pull/336
    • Release/v0.6.1 by @jasonbahl in https://github.com/wp-graphql/wp-graphql-acf/pull/338

    Full Changelog: https://github.com/wp-graphql/wp-graphql-acf/compare/v0.6.0...v0.6.1

    Source code(tar.gz)
    Source code(zip)
    schema.graphql(299.76 KB)
  • v0.6.0(Sep 15, 2022)

    What's Changed

    • Fix: Internal server error 500 for relationship to non-published post by @rsm0128 in https://github.com/wp-graphql/wp-graphql-acf/pull/301
    • Use date_i18n() to set correct timezone for date time fields by @esamattis in https://github.com/wp-graphql/wp-graphql-acf/pull/299
    • feat: ACF v6 support by @jasonbahl in https://github.com/wp-graphql/wp-graphql-acf/pull/333
    • Fix deprecated error in PHP > 8.0.0 by @fedek6 in https://github.com/wp-graphql/wp-graphql-acf/pull/313
    • filter returned value with acf/format_value by @anacoelhovicente in https://github.com/wp-graphql/wp-graphql-acf/pull/309
    • Update README.md by @RodrigoTomeES in https://github.com/wp-graphql/wp-graphql-acf/pull/290
    • Release/v0.6.0 by @jasonbahl in https://github.com/wp-graphql/wp-graphql-acf/pull/335

    New Contributors

    • @fedek6 made their first contribution in https://github.com/wp-graphql/wp-graphql-acf/pull/313
    • @anacoelhovicente made their first contribution in https://github.com/wp-graphql/wp-graphql-acf/pull/309
    • @seripap made their first contribution in https://github.com/wp-graphql/wp-graphql-acf/pull/304
    • @RodrigoTomeES made their first contribution in https://github.com/wp-graphql/wp-graphql-acf/pull/290

    Full Changelog: https://github.com/wp-graphql/wp-graphql-acf/compare/v0.5.3...v0.6.0

    Source code(tar.gz)
    Source code(zip)
    schema.graphql(299.76 KB)
  • v0.5.3(Jul 19, 2021)

  • v0.5.2(Apr 28, 2021)

  • v0.5.1(Apr 23, 2021)

  • v0.5.0(Apr 22, 2021)

    Release Notes

    This release focuses primarily on Location Rules and how ACF Field Groups are mapped to the WPGraphQL Schema.

    Bugfixes / Chores

    • #174: Typo fix in README. Thanks @pickleat!
    • #175: Fixes problem with return type on Select fields. Thanks @ljanecek!
    • #191: Replaces deprecated acf_get_term_post_id() method. Thanks @sboerrigter!
    • #197: Adds URI to play nice with Github Plugin Updater
    • #235: Updates README to include docs for registering field groups in PHP. Thanks @XAce90!

    New Features / Big Changes

    LOCATION, LOCATION, LOCATION!!!

    This release primarily addresses issues related to Field Group location rules and adding field groups to the GraphQL Schema.

    Prior to this release, ACF Field Groups were added to the GraphQL Schema strictly by analyzing the ACF Location Rules for the field group(s) and attempting to map the field group to the Schema.

    Some rules are quite nuanced and hard to translate, and in some cases this meant that the Field Group would simply not show up in the Schema, or in other cases the field group wouldn't show exactly where you wanted.

    This release brings a new way of mapping ACF Field Groups to the WPGraphQL Schema.

    It still uses ACF Location Rules to try and "guess" where in the Schema the field group should show, but now it shows you where it will be and allows you to opt-out of the auto-mapping and set the GraphQL Types the field group should show on manually.

    πŸŽ₯ πŸ‘‰ This video walks through this new functionality: https://youtu.be/VvrZGrcwv0Y

    Closes the following issues:

    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/58
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/149
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/169
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/206
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/76
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/135
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/198
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/189
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/186
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/188
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/210
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/22
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/42
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/52
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/65
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/127
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/132
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/162
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/203
    • closes https://github.com/wp-graphql/wp-graphql-acf/issues/233

    πŸ“£ HUGE shout out to @drewbaker @rsm0128 and @funkhaus for putting a lot of time and energy into Location Rule revamp. Would not be where it is without your work!!! πŸ™ŒπŸ»

    Source code(tar.gz)
    Source code(zip)
  • v0.4.1(Jan 19, 2021)

    Release Notes

    Bugfix

    • (#205): Fixes a bug where Flex Fields and Repeater Fields were not properly showing in when requesting posts as Previews. (see issue: #202)
    Source code(tar.gz)
    Source code(zip)
  • v0.4.0(Oct 22, 2020)

    Release Notes

    Breaking Change

    • (#172) changes "range" field from Integer to Float. Thanks @BronsonQuick!

    Bugfix

    • (#168) fixes memory leak. Thanks @acburdine!
    Source code(tar.gz)
    Source code(zip)
  • v0.3.5(Jul 27, 2020)

    Release Notes

    This adds support for ACF Fields to be shown with WPGraphQL Preview nodes. ACF revises meta, so when WPGraphQL returns a preview node, it uses the revised fields for ACF, where "normal" meta fields use the parent node's meta because "normal" meta is not revised.

    GUTENBERG NOTE:

    Gutenberg (the new WordPress block editor) currently has a bug that's causing meta to not be revised after posts are published, so this feature (previewing ACF meta) only works when using the Classic editor

    Source code(tar.gz)
    Source code(zip)
  • v0.3.4(Jun 18, 2020)

    Release Notes

    Bugfix

    • Fixes Taxonomy field to allow multi-select. Thanks @seagyn
    • Update typo in docs Thanks @davidshq
    • Update docs referencing how to install with Composer
    Source code(tar.gz)
    Source code(zip)
  • v0.3.3(Apr 27, 2020)

  • v0.3.2(Apr 17, 2020)

    Release Notes

    • Add graphql_field_name support for options pages. Thanks @esamattis!
    • Fix bug with datetime fields on options pages. Follow-up on #108
    Source code(tar.gz)
    Source code(zip)
  • v0.3.1(Dec 13, 2019)

    Release Notes

    New Features

    • Add graphql_acf_post_object_source filter (thanks @kidunot89)
    • add new fields for the google map field (thanks @dsturm!)
    • add new explicit "graphql_field_name" option for fields (thanks @esamattis!)

    Bugfixes

    • Fix bug with textarea not properly applying wpautop
    • Fix bug where flex fields without layouts configured were being added to the Schema (#94)
    Source code(tar.gz)
    Source code(zip)
  • v0.3.0(Dec 13, 2019)

    Release Notes

    This release adds compatibility to WPGraphQL v0.4.0

    NOTE: This release makes some changes that require WPGraphQL v0.4.0. Please read the release notes for WPGraphQL v0.4.0 as it might cause some breaking changes for other extensions.

    New Features

    • pass $field_config through a filter. Thanks @doublesharp!
    • updates to play nice with WooGraphQL. Thanks @kidunot89
    • add graphql_acf_field_value filter. Thanks @epeli
    Source code(tar.gz)
    Source code(zip)
  • v0.2.1(Aug 12, 2019)

    Release Notes

    Bugfixes

    • fix issue with assigning field group to individual post. Thanks @jayarnielsen!
    • fix issue with date/times in repeaters. Thanks @speedpro!
    • fix bug with select fields set to allow multiple
    • fix bug where errors are thrown when field group is assigned to single post where the post_type is not set to "show_in_graphql"

    New Features / Enhancements

    • Prevent execution if WPGraphQL or ACF are not also active. Thanks @jacobarriola!
    • remove devDependencies from versioned code
    • set minimum PHP version to 7.0 in plugin file
    Source code(tar.gz)
    Source code(zip)
  • v0.2.0(Jul 24, 2019)

    This release changes the plugin from a licensed plugin to a fully free plugin with no code to check for valid licenses.

    Big shout out to @gatsbyjs for making this possible!

    Source code(tar.gz)
    Source code(zip)
  • v0.1.4(May 14, 2019)

    πŸš€ Release Notes

    • Fixes bug with WYSIWYG fields nested in Flex Fields and Repeater Fields not properly resolving
    • Adds support for assigning ACF Field Groups to attachments (MediaItems)
    Source code(tar.gz)
    Source code(zip)
  • v0.1.3(May 8, 2019)

    πŸš€ Release Notes

    Breaking Changes

    • Shouldn't be any, but please let us know if you discover something

    New Features

    • Add support for Menu as a Field Group Location
    • Add support for MenuItem as a Field Group Location
    • Add support for Terms (Category, Tag, custom) as a Field Group Location
    • Add support for Comments as a Field Group Location

    Bugfixes & Misc cleanup

    • apply the_content filter to wysiwyg fields. Thanks for the suggestion @drewbaker
    • fix bug with radio field type not showing the show_in_graphql option in the ACF UI
    • Add .gitattributes to cleanup the zip file that is processed by git
    • remove unused Gruntfile.js
    Source code(tar.gz)
    Source code(zip)
  • v0.1.2(Apr 26, 2019)

    πŸš€ Release Notes

    πŸ›BUGFIXES:

    • Nested fields within Flex Fields were not properly showing. Thanks for reporting this one, @skaltenegger!

    Here's some info on what the bug was:

    By default, fields that are not set to "show_in_graphql" are not shown in in the Schema. There was a bug causing fields nested within a Flex Field Layout to default to not show in the GraphQL Schema.

    This release fixes that bug, so nested fields within Flex Field layouts are properly exposed to the Schema.

    Source code(tar.gz)
    Source code(zip)
Owner
WPGraphQL
An Open Source WordPress plugin that enables a GraphQL API for WordPress sites
WPGraphQL
Adds Settings to the Custom Post Type UI plugin to show Post Types in WPGraphQL

DEPRECATION NOTICE ?? Custom Post Type UI v1.9.0 introduced formal support for WPGraphQL!!! ?? With that, this plugin is being deprecated and will no

WPGraphQL 77 Aug 3, 2022
Gutenberg Custom Fields... wait what?

Gutenberg Custom Fields Gutenberg Custom Fields allows you to control the content of the Gutenberg edit screen by creating pre-filled templates. Navig

Riad Benguella 192 Dec 24, 2022
A custom WordPress nav walker class to fully implement the Twitter Bootstrap 4.0+ navigation style (v3-branch available for Bootstrap 3) in a custom theme using the WordPress built in menu manager.

WP Bootstrap Navwalker This code in the main repo branch is undergoing a big shakeup to bring it in line with recent standards and to merge and test t

WP Bootstrap 3.3k Jan 5, 2023
A WordPress package for updating custom plugins and themes based on an API response from a custom update server.

WordPress Update Handler A WordPress package for updating custom plugins and themes based on an JSON REST API response from a custom update server. Ch

WP Forge 7 Oct 5, 2022
Wordpress advance plugin with multi purposes features like live chat, custom post type, custom forms, word count etc

What is this? This is wordpress plugin which is created for the multi purpose uses. How to use? Simply install the plugin. Go to the plugin settigs pa

Amir Liaqat 2 Jun 23, 2022
Authentication for WPGraphQL using JWT (JSON Web Tokens)

WPGraphQL JWT Authentication This plugin extends the WPGraphQL plugin to provide authentication using JWT (JSON Web Tokens) JSON Web Tokens are an ope

WPGraphQL 268 Dec 31, 2022
Enable query locking for WPGraphQL by implementing persisted GraphQL queries.

?? WP GraphQL Lock This plugin enables query locking for WPGraphQL by implementing persisted GraphQL queries. Persisted GraphQL queries allow a GraphQ

Valu Digital 21 Oct 9, 2022
WPGraphQL Extension: Adds "meta_query" support to postObject connection queries using WP_Query

WPGraphQL Meta Query This plugin adds Meta_Query support to the WP GraphQL Plugin for postObject query args. Why is this an extension and not part of

WPGraphQL 42 Nov 10, 2022
[ALPHA] Implementation of persisted queries for WPGraphQL

WPGraphQL Persisted Queries Persisted GraphQL queries allow a GraphQL client to optimistically send a hash of the query instead of the full query; if

Quartz 18 Jun 20, 2022
Send emails via mutation using WpGraphQl

WPGraphQL Send Email Plugin One of the simple things about a traditional WordPress sites is sending emails, this plugin makes it easy to do this via a

Ashley Hitchcock 18 Aug 21, 2022
An WPGraphQL extension that adds SearchWP's query functionality to the GraphQL server

QL Search What is QL Search? An extension that integrates SearchWP into WPGraphQL. Quick Install Install & activate SearchWP v3.1.9+ Install & activat

Funkhaus 11 May 5, 2022
Structured content blocks for WPGraphQL

WPGraphQL Content Blocks (Structured Content) This WPGraphQL plugin returns a WordPress post’s content as a shallow tree of blocks and allows for some

Quartz 72 Oct 3, 2022
WPGraphQL Polylang Extension for WordPress

WPGraphQL Polylang Extension Extend WPGraphQL schema with language data from the Polylang plugin. Features For posts and terms (custom ones too!) Adds

Valu Digital 102 Dec 29, 2022
a wordpress plugin that improves wpgraphql usage together with wpml

WPGraphQL WPML Extension Contributors: rburgst Stable tag: 1.0.6 Tested up to: 5.6.1 Requires at least: 4.9 Requires PHP: 7.0 Requires WPGraphQL: 0.8.

null 42 Dec 15, 2022
WPGraphQL FacetWP integration plguin

WPGraphQL-FacetWP: WPGraphQL provider for FacetWP Quick Install Download and install like any WordPress plugin. Documentation The WPGraphQL documentat

null 31 Dec 11, 2022
WPGraphQL for Meta Box

WPGraphQL-MetaBox: WPGraphQL provider for Meta Box Quick Install Download and install like any WordPress plugin. Documentation The WPGraphQL documenta

null 25 Aug 8, 2022
This is an extension to the WPGraphQL plugin for Yoast SEO

WPGraphQl Yoast SEO Plugin Please note version 14 of the Yoast Plugin is a major update. If you are stuck on version of Yoast before V14 then use v3 o

Ashley Hitchcock 197 Dec 26, 2022
Add WooCommerce support and functionality to your WPGraphQL server

WPGraphQL WooCommerce (WooGraphQL) Docs β€’ AxisTaylor β€’ Join Slack Quick Install Install & activate WooCommerce Install & activate WPGraphQL Download t

WPGraphQL 546 Jan 2, 2023
Advanced Import : One Click Import for WordPress or Theme Demo Data

Advanced Import is a very flexible plugin which convenient user to import site data( posts, page, media and even widget and customizer option ).

Santosh Kunwar 1 Jan 18, 2022