You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2021. It is now read-only.
I recently upgraded to vs. 1.0.0 from 0.0.1-alpha.1 and now my baseUrl option is ignored. It was attempting to use localhost instead of the baseUrl. I had to revert back to 0.0.1-alpha.1, delete .cache and public in order to get it working again with my specified baseUrl.
{
resolve: `gatsby-source-wordpress`,
options: {
// your wordpress source
baseUrl: `http://[mywpdomain].com:8090`,
protocol: `http`,
// is it hosted on wordpress.com, or self-hosted?
hostingWPCOM: false,
// does your site use the Advanced Custom Fields Plugin?
useACF: true,
verboseOutput: false,
plugins: [
{
resolve: `gatsby-wordpress-inline-images`,
options: {
baseUrl: `http://[mywpdomain].com:8090`,
protocol: `http`,
maxWidth: 800,
},
},
],
},
},
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I recently upgraded to vs. 1.0.0 from 0.0.1-alpha.1 and now my baseUrl option is ignored. It was attempting to use localhost instead of the baseUrl. I had to revert back to 0.0.1-alpha.1, delete .cache and public in order to get it working again with my specified baseUrl.
The text was updated successfully, but these errors were encountered: