wp-graphql / wp-graphql-acf

WPGraphQL for Advanced Custom Fields

WPGraphQL

WPGraphQL is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site.

Below are some links to help you get started with WPGraphQL

• WPGraphQL.com
• Quick Start Guide
• Intro to GraphQL
• Intro to WordPress
• Join the WPGraphQL community on Discord

---

Install

• Requires PHP 7.1+
• Requires WordPress 5.0+

Quick Install

Follow the WPGraphQL Quick Start instructions to install and activate WPGraphQL Details here

Additional Documentation

• Project Overview
• Plugin Usage & Extension Documentation
• Development Testing & code Coverage
• Using Docker

Shout Outs

• Special thanks to Gatsby and WPEngine for allocating development resources to push the project forward!
• This plugin brings the power of GraphQL (http://graphql.org/) to WordPress.
• The plugin is built on top of the graphql-php library by Webonyx (https://github.com/webonyx/graphql-php) and makes use of the graphql-relay-php library by Ivome (https://github.com/ivome/graphql-relay-php/)
• Some of the concepts and code are based on the WordPress Rest API. Much love to the folks (https://github.com/orgs/WP-API/people) that put their blood, sweat and tears into the WP-API project, as it's been huge in moving WordPress forward as a platform and helped inspire and direct the development of WPGraphQL.
• Much love to Facebook® for open sourcing the GraphQL spec (https://facebook.github.io/graphql/), the amazing GraphiQL dev tools (https://github.com/graphql/graphiql), and maintaining the JavaScript GraphQL reference implementation (https://github.com/graphql/graphql-js)
• Much love to Apollo (Meteor Development Group) for their work on driving GraphQL forward and providing a lot of insight into how to design GraphQL schemas, etc. Check them out: http://www.apollodata.com/

Contributors

This project exists thanks to all the people who contribute. [Contribute].

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Privacy Policy

WPGraphQL uses Appsero SDK to collect some telemetry data upon user's confirmation. This helps us to troubleshoot problems faster & make product improvements.

Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users.

Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case.

Learn more about how Appsero collects and uses this data.

wp-graphql-acf's Issues

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"}

Sometimes Fields don't show until a Field Group is trashed :thinking:

2 people have reported that the fields are not showing in their Schema. Trashing the field group and restoring the group brings the fields back to the Schema.

minor formatting issues on class-config.php

Error activating plugin

I am getting the following error trying to activate the plugin added via git cloning into a WP 5.22

Parse error: syntax error, unexpected ':', expecting '{' in /Users/XXX/repos/bsr/website backup/wp-content/plugins/wp-graphql-acf/wp-graphql-acf.php on line 89

Post Object field showing an error

Please tell what am I doing wrong?

Feature Request: Return Value as set in ACF - value, label, or both (Array)

Was recently getting an array from a radio field. GraphQL returned the values as expected. But ACF has a setting to Return Value with options Value, Label, or Both (Array). Having the ability to return the Label would have facilitated my data needs.

Screenshot for reference:

Relationships field error

Hi

Sorry in a rush so I will try to add more detail and a reproduction tomorrow.

I just came across an issue whereby a query for a post with a relationship field broke (returned internal server error). This went away after updating the post - I'm assuming the relationship broke somehow maybe because a project was updated. This may be an ACF issue rather than being to do with this plugin, but thought it worth mentioning.

Flexible Content query's not working

Create a field group with the Wp-GQL key of acfSocialLinks (also would be great if this could be acf-social-links). Then create a Flexible Content layout. See my screenshot. You'll see that you can't actually get the query to work.

remove unneeded package.json

ACF video type media returns sourceUrl as false

ACF Image or File query response returns false for sourceUrl when the file is a video (tested with .webm and .mp4 formats).

Steps to reproduce:

• add a ACF Image or File field
• upload and save a video file (for example .mp4) to that field
• query the field and display sourceUrl

Mentions:

• guid returns the correct path to the file
• sourceUrl returns false

"testMedia": { "sourceUrl": "false", "title": "test", "guid": "http://test.test/wp-content/uploads/2019/06/test.mp4" },

Support individual terms location

When an ACF Field Group is assigned to an individual term, the fields should show in the GraphQL Schema

ACF Options Page GraphQL support

Hi,
I set up new options page and associate custom fields with it by using acf_add_options_page()
Now it looks like GraphQL schema doesn't cover this type of page.

Am I right or I'm doing something wrong?

Are you planing to introduce support for this page type?

Regards

wp-graphql-acf not showing Group field

I am building a site using gatsbyjs and wp-graphql-acf and ran into an issue.

I created a Group and added a subfield I am able to query it out in WP-GraphiQL but am not able to query that field in GraphiQL ( localhost:8000/___graphql ).

Has anyone else ran into this when using ACF Group field?

Thank You

Feature request: add support for custom acf field types

It would be great to have a filter in \WPGraphQL\ACF\Config::add_field_group_fields inside the foreach loop, so I can register a type for a custom ACF field type.

Right now, there's a filter for wpgraphql_acf_supported_fields, so the custom field type can be "supported", but I don't see how to accomplish the next step without another filter in add_field_group_fields

WooCommerce relation

Hi,

I have a test project with a few CPT relations. Everything is working as expected but when I try to relate a WooCommerce product (I have the WC extension installed) it doesn't show up in GraphiQL. Am I missing something or is the WC extension not supported for relationships?

[
    'key' => 'field_membership_product_relationship',
    'name' => 'product_relationship',
    'label' => __('Product', 'tp-cpt'),
    'type' => 'post_object',
    'post_type' => [
        'product'
    ],
    'show_in_graphql' => true,
],

The same code for a CPT is working like a charm.

Relationship field throws errors when a related item has been deleted

When an item in a relationship has been deleted, querying for a relationship field will throw errors.

For example, if I create a post and set it to be related to "Dummy Post", then delete "Dummy Post", the relationship field query will throw an error because the Dummy Post doesn't actually exist anymore.

Feature Request: Allow queries to ACF fields specific to a Category

Feature

Category specific ACF fields are not currently available to query and need to be mapped.

Example

The below will not appear in our schema:

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?

Remove Freemius code for license checks

Now that the plugin is free, the Freemius dependency that checks for license activations should be removed.

New GraphQL fields not showing in the Schema

See attached file. I can find the acfEventFields in the Schema, but searching for the acfSubHead does not display. I see in another closed issue that I have to trash my Field Group first?

Add support for Github Updater

A while back I wanted to do this for my own plugin, because I saw it happen with a plugin also hosted on Github and I asked the maker of the plugin. The conversation can be found here, it goes way over my head and I myself didn't take the time to look in in myself (because my plugin rarely gets updated and it only used by me), but maybe someone here has a better understanding on how WP plugins work.

Compatibility with WPGraphQL v0.4.0

WPGraphQL v0.4.0 (upcoming) introduces some breaking changes to the TypeRegistry.

WPGraphQL for ACF will need some updates to play nice with the core WPGraphQL update.

The update to WPGraphQL v0.4.0 enables the GraphQL Schema to be cleared properly, enabling better integration tests with Codeception, which will severely increase the code quality of the core plugin and extensions such as ACF.

---

The changes needed for this extension to play nice are pretty minor:

• Hook the main Config to init_graphql_type_registry instead of graphql_register_types
• Have the Config class accept TypeRegistry as an argument, and set it in the class as a class var
• Replace instances of TypeRegistry:: static method calls with $this->type_registry (using the ^ instance passed into the class)
• Replace the resolveType methods to use the type_registry passed to the class instead of static Types:: methods
• Refactor tests to be more granular (the result and primary goal of the new WPGraphQL::__clear_schema() ability). . .now tests can be MUCH more granular, readable, and maintainable, instead of registering everything all up front, individual tests can register exactly what they need!

Taxnomy returns empty [] unless 'Appearance' is set to Multi Select

Queries for Taxonomy fields return an empty array if not set to Multi Select appearance in the ACF Field Settings.

{ 
    taxonomyName {
        ... on TaxonomyName {
            id
            name
        }
}

will return

{
"taxonomyName": []
}

Changing Return Value doesn't seem to have any bearing on the success of the query.

A quick fix I've just tried is to extend class-config.php at line 586 to the following

if ( ! empty( $value ) && is_array( $value ) ) {
    foreach ( $value as $term ) {
		 $terms[] = DataSource::resolve_term_object( (int) $term, $context );
	}
}
else
{
    $terms[] = DataSource::resolve_term_object( (int) $value, $context );
}

I haven't done any real testing here though, so welcome any other input if anyone else has experience with a similar problem.

Multiple users ACF field not working

wp-graphql-acf/src/class-config.php

Line 576 in 85ec7dd

return DataSource::resolve_user( (int) $value, $context );

I did a test with this code and it worked fine.

`
case 'user':
$field_config = [
'type' => [ 'list_of' => 'User' ],
'resolve' => function( $root, $args, $context, $info ) use ( $acf_field ) {
$value = $this->get_acf_field_value( $root, $acf_field );
$users = [];

            if ( ! empty( $value ) && is_array( $value ) ) {
                foreach ( $value as $user ) {
                    $users[] = DataSource::resolve_user( (int) $user, $context );
                }
            }

            return $users;
    },

];
break;
`

ACF Repeater fields date or date time are null

Any date format inside of repeater field are null

WP Graphql

WP REST API

Reusable Fragments on Field Groups shared betweeen Post Types

Currently I have registered 12 Post Types that need to share a single ACF field group, namely a large ACF "Flexible Content" field type.

All ACF Fields seem to be prefixed by the PostType name ( ie Page_ and Article_ below), which means it is not possible to create GraphQL Fragments to share between post types, leading to a lot of repetition.

export const contentQueryOne = graphql`
  query MyQuery {
    pages {
      nodes {
        acfRichContent {
          richContent {
            ... on Page_Acfrichcontent_RichContent_CardLinks {
              cardField
            }
            ... on Page_Acfrichcontent_RichContent_KeyStats {
              statField
            }
            ... on Page_Acfrichcontent_RichContent_RelatedResources {
              resourceField
            }
            ... on Page_Acfrichcontent_RichContent_Downloads {
              downloadField
            }
          }
        }
      }
    }
    articles {
      nodes {
        acfRichContent {
          richContent {
            ... on Article_Acfrichcontent_RichContent_CardLinks {
              cardField
            }
            ... on Article_Acfrichcontent_RichContent_KeyStats {
              statField
            }
            ... on Article_Acfrichcontent_RichContent_RelatedResources {
              resourceField
            }
            ... on Article_Acfrichcontent_RichContent_Downloads {
              downloadField
            }
          }
        }
      }
    }
  }
`

... and so on x 10 more prefixed post types.

Ideally it would be possible to create a single fragment that can be used across any post type that might want it. Something like the below...

export const richContent = graphql`
  fragment RichContent on Acfrichcontent_RichContent {
    RichContent {
      ... on Acfrichcontent_RichContent_CardLinks {
        cardField
      }
      ... on Acfrichcontent_RichContent_KeyStats {
        statField
      }
      ... on Acfrichcontent_RichContent_RelatedResources {
        resourceField
      }
      ... on Acfrichcontent_RichContent_Downloads {
        downloadField
      }
    }
  }
`

export const contentQuery = graphql`
  query MyQuery {
    pages {
      nodes {
        acfRichContent {
          ...RichContent
        }
      }
    }
    articles {
      nodes {
        acfRichContent {
          ...RichContent
        }
      }
    }
    news {
      nodes {
        acfRichContent {
          ...RichContent
        }
      }
    }
    events {
      nodes {
        acfRichContent {
          ...RichContent
        }
      }
    }
  }
`

Am i missing something, or should that be possible?

New Feature: Support for User fields

Feature request: mutation

Sup, wouldn't it be awesome if wp-graphql-acf supported mutation? since acf doesn't support post/get value in api as far as I know, I tried, very hard even with ACF to REST API plugin

Clone field support?

"The Clone field needs some more assessment to determine if it can properly be supported."

Is there a discussion about this anywhere public?

Our use case is we often create an ACF group called Flexible Content (which contains a flexible content field with different options defined in it) and then Clone that into different content types.

When I query this using the plugin, I get an empty array back.

Not works with Acf crop image plugin

I try use https://github.com/andersthorborg/ACF-Image-Crop . but not show in graphql.

Plugin should not execute if ACF and WPGraphQL are both not active

Currently we check to see if ACF and WPGraphQL are both active, and if not we show an admin notice. . .but we still attempt to make use of ACF functions, even if it's not active.

In addition to the notice, we should also prevent further execution to avoid fatal errors.

https://github.com/wp-graphql/wp-graphql-acf/blob/master/wp-graphql-acf.php#L52

ACF Field Groups not showing when set to show on equal page filter

When creating ACF Field Groups and setting the filter for instance as:

Show this field group if:
Page is equal to SELECTED_PAGE

The ACF field isn't queryable through the pageBy with uri. This is the example of the query I ran to find this issue:

{
  pageBy(uri: "live-act") {
    id
    artistCategory {
      category_video
    }
  }
}

Which returns the error:

{
  "errors": [
    {
      "message": "Cannot query field \"artistCategory\" on type \"Page\".",
      "category": "graphql",
      "locations": [
        {
          "line": 4,
          "column": 5
        }
      ]
    }
  ]
}

If one remove the filter and set it to display on all pages it is perfectly queryable in the GraphQL schema.

remove unused yarn.lock

Feature Request: Expose Field Choices

Allow to get choices from an ACF field that has them, for example, Checkbox, Radio, Select, and Button Group. Screenshot shows an example of what should be returned.

Select field doesn't work if `Select Multiple Values` is set to yes

This issue was reported via email. Below is the info provided in the email:

The Select Field Type seems to only work if the "Select Multiple Values" box is set to no. If its set to "yes" an Internal Server Error pops up when queried.

I've attached a screenshot of my query and the error message as well as a make shift JSON file.

"Fillings" and "Flavors" are the 2 fields I would like to use Select, for but Im just using a Text Area for now. The selectField is the only Select in the query.

I've labeled the attachments so you can see it works if set to "No Multiple Values". Otherwise I've been super impressed with the plugin and I'm really excited for its future.

I hope this helps. If you figure it out please let me know or if theres anything else you need from me just let me know.

---

![Uploading yesMultipleValues.png…]()

ACF not showing when rule is set to user role

When creating an ACF and setting the rules as:
Show this field group if:
User role is equal to ROLE
The ACF field isn't queryable through the viewer (when authenticated). Here is an example query :

query getViewer {
  viewer {
    id
    username
    name
    userId
    myacf
  }
}

This returns this error :

{
  "errors": [
    {
      "message": "Cannot query field \"myacf\" on type \"User\".",
      "category": "graphql",
      "locations": [
        {
          "line": 7,
          "column": 5
        }
      ]
    }
  ]
}

It works when the rule is set as User role is equal to All, but will show on every user profile, which is not ideal.

WYSIWYG & Textareas not getting auto p and br tags

If you use the WYSIWYG or Textarea fields, normally the output would get the WordPress auto <p> and <br> tags applied to them. The textarea field actually has a dropdown to opt into no formatting, or just br, or both p or br.

It seems WYSIWYG should always be set to auto-p (basically behave the same as regular post_content fields, and the textarea should respect the dropdown settings.

WYSIWYG output should run through this filter: apply_filters('the_content', $output);

And textarea should run through the different options of this function it seems:
https://codex.wordpress.org/Function_Reference/wpautop

Multiple values Post Object ACF field not working

Originally posted here: wp-graphql/wp-graphql#939

---

When using a multiple values Post Object ACF field, WPGraphQL return an empty object instead of the list of post objects.

Steps to reproduce:

• Make a multiple values Post Object ACF field
• Try to query it

Query taxonomy term inside ACF Repeater field

Hi,

I have an ACF Repeater field, with different types of fields inside of it. One of them is a WordPress Taxonomy, for which I cannot find how to return the values of the terms on it, it keeps returning just empty [] values.

Here some screenshots to illustrate my ACF fields setup.

Here my query and the results from GraphQL, where it returns empty values for the taxonomy Indicator, despite that in my query I'm requesting their taxonomy ID and name.

What I'm missing here?

BUG: When ACF Field Group is assigned to single Post of a Post Type not set to show_in_grapql

When an ACF Field Group is assigned to a single Post (of any post type), if the post_type is not set to "show_in_graphql" errors are thrown.

Dynamically check field groups against visibility conditions

@jasonbahl There may be a way around this, but I noticed that the registering if field groups within WPGraphQL is a bit limited. For instance:

https://github.com/wp-graphql/wp-graphql-acf/blob/release/v0.2.1/src/class-config.php#L142-L146

This section checks if the post_type is equal to a page, but I have two conditions on this particular Field Group:

1. Is of post type page
2. Is a specific page template.

This seems more like a limitation of ACF, but when running acf_get_field_groups( [ 'post_type' => 'page' ] ), field groups with ONLY that condition show. If there are more conditions (such as a page template type), the function returns empty.

I need ACF fields added to the GraphQL Schema of a page that is also a specific template. For now, it seems like I may have to add these myself? Please let me know if I'm doing something wrong or if this is a known limitation.

Thanks!

Support for multiple values on User Field Type

It does not work when the multiple values feature is enabled.

Support for single posts/pages is broken

Errors are thrown when a field group is assigned to a single post of a custom post type

Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Undefined index: post_type in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1178 Notice: Undefined index: field_group in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1179 Notice: Undefined index: post_id in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1180 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Undefined index: description in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1206 Notice: Undefined index: title in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Undefined index: description in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1206 Notice: Undefined index: title in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 Notice: Trying to get property 'graphql_plural_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1209 Notice: Trying to get property 'graphql_single_name' of non-object in /var/www/html/wp-content/plugins/wp-graphql-acf/src/class-config.php on line 1217 {"errors":[{"message":"GraphQL Request must include at least one of those two parameters: \"query\" or \"queryId\"","category":"request"}]}

Make Connections for Repeaters / Flex Fields

Some fields in ACF return lists. Sometimes those lists would be nice to paginate instead of get the entire list back.

Flex Fields, Repeaters and other fields that return lists could/should return connections and support pagination, and at some point filters, etc

Feature Request: Expose ACF fields defined on attachments

It is possible to extend attachment with custom fields. These are currently not exposed through wp-graphql-acf, although it would be great to have!

If repeater image field is empty, throws internal server error

I was trying to query a repeater field that had a title and an image. If the image was empty, then it would error.

            headerGallery {
                text
                image {
                    id
                }
            }

If image is not set in the CMS, this will return an internal server error.

Composer and MU-plugin

Hey,
When you are guys planning to push this plugin to the Composer?
Currently, this plugin requires wp-graphql v3.2 to be installed but this version doesn't exist in Composer either.

Another problem is that when I keep ACF, GraphQL and GraphQL ACF as MU plugin it shows error in admin panel that I need to Install and activate them, even if it's already done.

And the last issue is with activating GraphQL ACF. Even if I have all plugins correct version as described in your documentation and installed in usual "plugin" directory it gives me an error: "version cannot be empty."

Please help.

Install free version asks for license key

Is the conversion of the plugin from being premium to free an ongoing development, or is there any nescessary things we have to do in order to avoid the license key input on installation?

ACF page link & Taxonomy link - cant access values chosen

It is listed as supported, but requires extra {} in the query, but the suggestion of graphiql is always "__typename" and won't suggest other fields. Perhaps I just need to know the underlying default values in the array.

{
  events {
    nodes {
      title
     content
      attr {  //ACF
        eventLink
        eventLinkLabel
        internalEventLink { //<< THIS BAD BOY RIGHT HERE
					__typename          
        }
        datetime
        endTime
        audience        
        venueLocation
        eventImage {
          sourceUrl//<< OLD MATE HERE SUGGESTED ME A FEILD A-OK
        }
      	bigOrSmall
      }
    }
  }
}

Feature request: Sort / Order by custom field.

Currently, there is no way to sort posts by custom fields. So in case scenario that is probably quite common where for example, you have Custom Post Type: Events and then you would add Advanced Custom Field: Start Date. You're not able to sort by Start Date.

I guess there are some workarounds but it would be great to have Sort by ACF.