Closed amantiwari1 closed 3 years ago
Run npm i gatsby-source-wordpress-experimental@latest
That seemed to fix it for me!
Hi @amantiwari1 , this isn't a bug. If you follow the instructions in the error message it will work. Either you need to upgrade your version of gatsby-source-wordpress-experimental
or you need to upgrade your version of WPGatsby.
EDIT: you're on the latest version of the source plugin so you need to upgrade WPGatsby
Hi, @TylerBarnes and @8ctopotamus , Thanks for responding, It is working for now for same latest version of WPGatsby and gatsby-source-wordpress-experimental
and upgraded in WPGraphQL 1.0.5 No Wonder!!
I have this behavior today, what I did instead.
npm remove gatsby-source-wordpress-experimental --save
npm install gatsby-source-wordpress --save
update gatsby-config.js for the said plugin name, then working as expected.
Reason behind for this approach was due to the deprecation message in cli.
Upgrade/deprecation notice:
Hi there! 👋 thank you so much for being a beta/alpha tester of this plugin!
You've helped us bring a much more stable WordPress integration to Gatsby and we're very thankful for that!
We've shipped this plugin as `gatsby-source-wordpress@4.0.0`.
`gatsby-source-wordpress-experimental` is now deprecated.
Please upgrade by npm/yarn installing the latest version of the stable plugin and updating your gatsby-config.js to include the stable plugin name.
We've chosen this point to release this plugin as a stable release not because there are no bugs (all software has some bugs), but because this plugin is far more stable than the last major version of `gatsby-source-wordpress`.
Note that we will continue fixing Github issues you've opened in the -experimental repo - those are not forgotten and will be transferred to the Gatsby monorepo.
Thank you! 💜
How to fix it? I cant find answer in internet
package.json
wordpress plugins -