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?

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.

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

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

After

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

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..?

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:

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.

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 :

Graphql schema :

Graphql query:

Custom field group :

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

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

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

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

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.

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"

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.

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

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

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

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

GraphiQL result I only get the image number, not the url... (in this case, 37)

Is there any way I can get the image url?

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?