Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0 #37729

Haldaug · 2023-03-09T12:48:25Z

Preliminary Checks

This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

An error occurs during parallel query running after upgrading the Word Press plugin WPGraphQL to 1.14.0, failing the build. I suspect that the update included some breaking changes for gatsby-source-wordpress.

Everything works as expected after downgrading back to 1.13.1

Reproduction Link

/

Steps to Reproduce

Upgrade WPGraphQL from 1.13.10 to 1.14.0
Run a clean build

Expected Result

A successful build

Actual Result

I get the following error:
ERROR #11321 API.NODE.EXECUTION "gatsby-node.js" threw an error while running the createPages lifecycle: Interface field WpConnectionType.nodes expected but WpEnqueuedScriptConnectionType does not provide it. Interface field WpConnectionType.nodes expected but WpEnqueuedStylesheetConnectionType does not provide it. Interface field WpConnectionType.nodes expected but WpActionMonitorActionConnectionType does not provide it. Interface field WpConnectionType.nodes expected but WpPluginConnectionType does not provide it. Interface field WpConnectionType.nodes expected but WpThemeConnectionType does not provide it.

You can find an example of a failed build here: https://www.gatsbyjs.com/dashboard/2ed6779b-2fc9-4c4f-b7db-3aac04ebbde8/sites/cef43953-59d5-4aa4-862b-7a8d057182ef/builds/697abd16-42d4-46d8-a1a3-d80b30d3471d/details?returnTo=%2Fdashboard%2F2ed6779b-2fc9-4c4f-b7db-3aac04ebbde8%2Fsites%2Fcef43953-59d5-4aa4-862b-7a8d057182ef%2FcmsPreview#rawLogs

Environment

System:
    OS: Linux 5.10 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1260P
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 19.3.0 - ~/.nvm/versions/node/v19.3.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.2.0 - ~/.nvm/versions/node/v19.3.0/bin/npm
  npmPackages:
    gatsby: ^5.0.1 => 5.7.0 
    gatsby-plugin-algolia: ^1.0.0 => 1.0.3 
    gatsby-plugin-exclude: ^1.0.2 => 1.0.2 
    gatsby-plugin-feed: ^5.1.0 => 5.7.0 
    gatsby-plugin-gatsby-cloud: ^5.1.0 => 5.7.0 
    gatsby-plugin-google-gtag: ^5.1.0 => 5.7.0 
    gatsby-plugin-image: ^3.1.0 => 3.7.0 
    gatsby-plugin-manifest: ^5.1.0 => 5.7.0 
    gatsby-plugin-no-sourcemaps: ^5.1.0 => 5.7.0 
    gatsby-plugin-perf-budgets: ^0.0.18 => 0.0.18 
    gatsby-plugin-postcss: ^6.1.0 => 6.7.0 
    gatsby-plugin-react-svg: ^3.3.0 => 3.3.0 
    gatsby-plugin-sharp: ^5.1.0 => 5.7.0 
    gatsby-plugin-sitemap: ^6.1.0 => 6.7.0 
    gatsby-plugin-webpack-bundle-analyser-v2: ^1.1.30 => 1.1.30 
    gatsby-source-filesystem: ^5.1.0 => 5.7.0 
    gatsby-source-wordpress: ^7.2.3 => 7.7.0 
    gatsby-transformer-sharp: ^5.1.0 => 5.7.0 
  npmGlobalPackages:
    gatsby-cli: 5.3.1

Config Flags

No response

The text was updated successfully, but these errors were encountered:

mrcsmcln · 2023-03-10T20:04:31Z

This exact issue is happening for me as well.

mikeriley131 · 2023-03-11T16:21:06Z

Same, I just started getting this yesterday after making no changes other than the WP GraphQL upgrade to 1.14.0.
Rolling back to 1.13.10 resolves the issue.

kylelondonuk · 2023-03-14T16:29:43Z

Same issue for me. Will roll back to 1.13.10

TylerBarnes · 2023-03-15T00:04:31Z

It appears to be a problem with the way source-wordpress is caching the remote schema. Certain types are omitted by default (because they don't work in Gatsby) but those types are only being omitted on the initial build and then are included in cached builds. When they're included they then break the schema because they're not properly implementing their interfaces since those types weren't supposed to exist anyway.

I've added some logic to catch when the generated schema doesn't match the previous schema and fail the build with a helpful error and type diffs, so that this will be more obvious in the future if it happens again. I'm also fixing the issue though and I should have a PR up tomorrow or the next day

TylerBarnes · 2023-03-16T01:13:42Z

I have a PR open fixing this ☝️ and there's a canary available as gatsby-source-wordpress@7.8.0-alpha-wp-inconsistent-schema.29 for anyone who needs it asap!

TylerBarnes · 2023-03-16T22:42:07Z

I marked the PR to be back ported for Gatsby 4 & 5 but check my previous comment for anyone who needs the fix right away

Fix for this error... Error: Interface field WpConnectionType.nodes expected but WpEnqueuedScriptConnectionType does not provide it. Temporarily using gatsby-source-wordpress@7.8.0-alpha-wp-inconsistent-schema.29 because of gatsbyjs/gatsby#37729 (comment)"

DanielRiveraHQ · 2023-04-28T15:10:59Z

I tried this, and the issue persists. On a fresh build, some nodes are missing, but if I go to Wordpress and save the content missing while I'm running gatsby development, it appears. @TylerBarnes

TylerBarnes · 2023-04-28T16:08:54Z

@DanielRiveraHQ are you able to share a reproduction with me? Sharing it privately works too (tyler@gatsbyjs.com)

dishpanda · 2023-05-28T00:28:09Z

Thanks for the canary fix, worked for me!

philJohnson · 2023-05-31T23:28:08Z

@TylerBarnes I'm also getting this issue. Looking at getting a reproduction however I've found that the issue occurs specifically when I exclude types in my config. I've attached the config below.

{
      resolve: `gatsby-source-wordpress`,
      options: {
        url: process.env.GATSBY_GRAPHQL_API_URL,
        schema: {
          timeout: 60000,
          perPage: 50,
          requestConcurrency: 15,
          previewRequestConcurrency: 5
        },
        html: {
          useGatsbyImage: false,
          createStaticFiles: false
        },
        type: {
          MediaItem: {
            createFileNodes: false
          },
           UserRole: {
             exclude: true
           },
           Comment: {
             exclude: true
          }
        },
        develop: {
          hardCacheMediaFiles: true
        }
      }
    },
    ```
    
 If I include comments and user roles then I no longer get an issue.

DanielRiveraHQ · 2023-06-01T00:18:13Z

@philJohnson I'll check if that solution works! 🙏

ibjorn · 2023-09-09T10:08:12Z

@TylerBarnes I'm also getting this issue. Looking at getting a reproduction however I've found that the issue occurs specifically when I exclude types in my config. I've attached the config below.

{
      resolve: `gatsby-source-wordpress`,
      options: {
        url: process.env.GATSBY_GRAPHQL_API_URL,
        schema: {
          timeout: 60000,
          perPage: 50,
          requestConcurrency: 15,
          previewRequestConcurrency: 5
        },
        html: {
          useGatsbyImage: false,
          createStaticFiles: false
        },
        type: {
          MediaItem: {
            createFileNodes: false
          },
           UserRole: {
             exclude: true
           },
           Comment: {
             exclude: true
          }
        },
        develop: {
          hardCacheMediaFiles: true
        }
      }
    },
    ```
    
 If I include comments and user roles then I no longer get an issue.

Removing type: {...} entirely worked for me. I was only using it for excludes anyway.

maghaffar · 2024-04-25T14:13:56Z

I have a PR open fixing this ☝️ and there's a canary available as gatsby-source-wordpress@7.8.0-alpha-wp-inconsistent-schema.29 for anyone who needs it asap!

I am still getting this error in 2024. Did'nt you resolved the issue?. I have upgraded my WPGraphql version and after that I am getting the error.
Do we have a permanent solution?

maghaffar · 2024-04-25T14:15:40Z

@TylerBarnes Please help me in resolving this. I want a permanent solution rather than changing my gatsby-source-wordpress version to the specific version you mentioned above

TylerBarnes · 2024-04-25T23:44:12Z

@maghaffar I'm not maintaining this repo anymore but the fix was released in Gatsby 4 and 5 nearly a year ago

maghaffar · 2024-04-26T06:08:21Z

@TylerBarnes Can you please mention who is maintaining the repo. I think that the it is needed to fix this again with WPGraphql 1.24.0.

Haldaug added the type: bug An issue or pull request relating to a bug in Gatsby label Mar 9, 2023

gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Mar 9, 2023

pieh added topic: source-wordpress Related to Gatsby's integration with WordPress and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Mar 10, 2023

TylerBarnes self-assigned this Mar 14, 2023

TylerBarnes mentioned this issue Mar 14, 2023

Interface field type error after upgrading from Gatsby v2 to v5 and using V 1.14 wp-graphql/wp-graphql#2760

Closed

3 tasks

TylerBarnes mentioned this issue Mar 16, 2023

fix(gatsby-source-wordpress): prevent inconsistent schema customization #37749

Merged

TylerBarnes closed this as completed in #37749 Mar 16, 2023

TylerBarnes mentioned this issue Mar 18, 2023

Upcoming release bug: ContentNode interface expects fields that some implementing types don't provide wp-graphql/wp-graphql#1116

Closed

ibjorn mentioned this issue Sep 9, 2023

The remote WPGraphQL schema hasn't changed but local generated type definitions have. #37931

Closed

2 tasks

justlevine mentioned this issue Apr 26, 2024

WPGraphql fetching duplicated nodes in Gatsby wp-graphql/wp-graphql#3105

Closed

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0 #37729

Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0 #37729

Haldaug commented Mar 9, 2023 •

edited

Loading

mrcsmcln commented Mar 10, 2023

mikeriley131 commented Mar 11, 2023 •

edited

Loading

kylelondonuk commented Mar 14, 2023

TylerBarnes commented Mar 15, 2023

TylerBarnes commented Mar 16, 2023

TylerBarnes commented Mar 16, 2023

DanielRiveraHQ commented Apr 28, 2023 •

edited

Loading

TylerBarnes commented Apr 28, 2023

dishpanda commented May 28, 2023

philJohnson commented May 31, 2023

DanielRiveraHQ commented Jun 1, 2023

ibjorn commented Sep 9, 2023

maghaffar commented Apr 25, 2024

maghaffar commented Apr 25, 2024 •

edited

Loading

TylerBarnes commented Apr 25, 2024

maghaffar commented Apr 26, 2024

Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0 #37729

Gatsby-source-wordpress: ERROR #11321 after upgrading WPGraphQL to 1.14.0 #37729

Comments

Haldaug commented Mar 9, 2023 • edited Loading

Preliminary Checks

Description

Reproduction Link

Steps to Reproduce

Expected Result

Actual Result

Environment

Config Flags

mrcsmcln commented Mar 10, 2023

mikeriley131 commented Mar 11, 2023 • edited Loading

kylelondonuk commented Mar 14, 2023

TylerBarnes commented Mar 15, 2023

TylerBarnes commented Mar 16, 2023

TylerBarnes commented Mar 16, 2023

DanielRiveraHQ commented Apr 28, 2023 • edited Loading

TylerBarnes commented Apr 28, 2023

dishpanda commented May 28, 2023

philJohnson commented May 31, 2023

DanielRiveraHQ commented Jun 1, 2023

ibjorn commented Sep 9, 2023

maghaffar commented Apr 25, 2024

maghaffar commented Apr 25, 2024 • edited Loading

TylerBarnes commented Apr 25, 2024

maghaffar commented Apr 26, 2024

Haldaug commented Mar 9, 2023 •

edited

Loading

mikeriley131 commented Mar 11, 2023 •

edited

Loading

DanielRiveraHQ commented Apr 28, 2023 •

edited

Loading

maghaffar commented Apr 25, 2024 •

edited

Loading