gatsbyjs / gatsby-source-wordpress-experimental

The upcoming v4 of gatsby-source-wordpress, currently in beta
MIT License
385 stars 100 forks source link

Number of Pages fetched limited to 35, requesting more results in 0 #414

Closed hawkstein closed 3 years ago

hawkstein commented 3 years ago

I'm using gatsby-source-wordpress-experimental v7.0.0 and have been able to successfully pull down pages from our Wordpress server, initially I'd set the limit to 35 or lower but now when I increase this amount, zero pages are fetched.

Page: {
   limit:
       process.env.NODE_ENV === `development`
           ? 35
            : process.env.WP_PAGE_LIMIT,
    },

There's no error message, just 0 Pages etc fetched and queryable. I've currently got the requestConcurrency set to 15:

schema: {
          requestConcurrency: 15,
        },

but no luck even if I incrementally lower it down to 1.

If we change the Pages modified date, then a different 35 is fetched as expected. 1000s of Comments and other nodes are pulled down. I've deleted the .wordpress-cache, gatsby clean'd before each run. I've deleted the limit option entirely, still the same.

What could be causing this? I can't find any WPGraphQL settings which might be the problem either.

Current plugin settings:

{
      resolve: `gatsby-source-wordpress-experimental`,
      options: {
        url: process.env.WPGRAPHQL_URL,
        develop: {
          hardCacheMediaFiles: true,
          hardCacheData: true,
          nodeUpdateInterval: 100_000_000, // set high here as we don't rely on changes to the data in development
        },
        schema: {
          requestConcurrency: 15,
        },
        type: {
          Page: {
            limit:
              process.env.NODE_ENV === `development`
                ? 100
                : process.env.WP_PAGE_LIMIT,
          },
        },
      },
    },

What additional info is required to replicate/diagnose? Thanks for any help in advance!

hawkstein commented 3 years ago

After working on this, it seems like it's a problem with the Wordpress Theme on the server. If it's disabled, then the plugin works fine.