-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hm #22
Comments
Same here. ERROR #11321 PLUGIN So it seems that frontend can't connect to backend... |
Problem was the trailing slash ("/") at the end of the URL. |
Can you elaborate on this? |
Hey! I'm having the exact same issue after following all your instructions. When i run
|
**Update for those who have encountered the same issue: ** I was trying to deploy this repo in a local enviroment. And the first error that gatsby was throwing was something about certificates issues that was preventing it from connecting to WP Graphql. So, after doing some research i found that if you put this flag in your .env you'll get around this error
This is telling Gatsby to skip SSL certificates validation (Take care of your SSL if you are not in a local env instead of doing this). Good luck! |
Got this running Yesterday because of @fuhranku's advice. |
Sadly this did not fix my issue, I'm still getting the same error, the docs are out of date, and the plugins could use an update. Tried to run this query on Wordpress > GraphiQL
but it says: I'm running WP from docker, the settings I have in gatsby-config.js are:
I access my WP instance by going to: http://localhost:8787 I've tried using the specific version of the plugins specified on the docs and also using their latest version, and I run into the same issue :/
Any help on this is highly appreciated :) |
I made exactly the same stuff like your readme but get this error on: site/ npm run dev
"gatsby-wordpress-theme-phoenix" threw an error while running the createPages lifecycle:
Cannot read property 'HWGraphQL' of undefined
8 | // Create all pages.
9 | exports.createPages = async ( { actions, graphql } ) => {
File: ../packages/gatsby-wordpress-theme-phoenix/gatsby-node.js:10:2
The text was updated successfully, but these errors were encountered: