wp-graphql / wp-graphql/wpgraphql-acf

Fragment error after adding Flexible Content to a page

Open
#239 2 comments 0 reactions 1 assignee View on GitHub

@jasonbahl is already working on this.

Since Sep 16, 2024.

close candidate
Dominant language
PHP
Stars
110
Forks
18
PR merge metrics
No merged PRs in 30d

Description

Description

I just added flexible content field to one of my templates and after I input some content in, I tried building my local it keep giving me this error on my terminal:

 ERROR  UNKNOWN

 gatsby-source-wordpress  (undefined) location: line 644, column: 12. location:
line 1007, column: 12
	 Cannot spread fragment "ContentNodeFragment" within itself via
PageFlexibleContentFragment.

 Error path: undefined

 If you haven't already, try adding define( 'GRAPHQL_DEBUG', true ); to your
wp-config.php for more detailed error messages.


 ERROR  UNKNOWN

Error from GraphQL IDE:

{
      "debugMessage": "GraphQL\\Type\\Schema::getImplementations(): Return value must be of type GraphQL\\Utils\\InterfaceImplementations, null returned",
      "message": "Internal server error",
      "extensions": {
        "category": "internal"
      },
Steps to reproduce

n/a

PHP or JSON export of the ACF Field Group(s)

acf-export-2024-09-14.json

Additional context

No response

WPGraphQL Version

1.28.1

WPGraphQL For ACF Version

2.4.1

ACF (Advanced Custom Fields) Version. Free or Pro?

v6.3.6 Pro

WordPress Version

6.6.1

PHP Version

8.2

Additional enviornment details

No response

Please confirm that you have searched existing issues in the repo.
  • Yes
Please confirm that you have disabled ALL plugins except for WPGraphQL, WPGraphQL For ACF, ACF, etc.
  • Yes
  • My issue is with compatibility with a specific WordPress plugin, and I have listed all my installed plugins (and version info) above.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.