Closed munnnnet closed 4 years ago
This usually happens when the schema is not correct. gatsby-starter-try-ghost
auto detects the schema from schema images provided by gatsby-source-ghost
. This auto detection works fine in my test cases but seems to fail with your use case.
In order to debug this issue, please provide me with your Content API keys. Only then will I be able to find the root cause. In addition, can you please provide the following information:
This is the whole script result from my terminal:
Bobohai:g222g Bobohai$ gatsby develop
success open and validate gatsby-configs - 0.706s
success load plugins - 2.027s
success onPreInit - 0.020s
success initialize cache - 0.014s
success copy gatsby files - 0.166s
success onPreBootstrap - 0.014s
success createSchemaCustomization - 0.037s
info GhostPost/feature_image/data-schema/https://images.unsplash.com/photo-15326
ERROR
(node:13985) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
ERROR
Error processing images in node Ghost__Post__5bbafb3cb7ec4135e42fce56:
failed to process https://images.unsplash.com/photo-1532630571098-79a3d222b00d?ixlib=rb-0.3.5&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=1080&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ&s=a88235003c40468403f936719134519d
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
info GhostPost/feature_image/how-to-set-up-google-analytics/https://images.unspl
info GhostPost/feature_image/website-analytics-tools/https://images.unsplash.com
info GhostPost/feature_image/ecommerce-seo/https://images.unsplash.com/photo-149
info GhostPost/feature_image/mobile-seo-strategy/https://images.unsplash.com/pho
info GhostPost/feature_image/indexing-algorithms/https://images.unsplash.com/pho
info GhostPost/feature_image/mobile-app-seo/https://images.unsplash.com/photo-15
info GhostPost/feature_image/not-set-google-analytics/https://images.unsplash.co
info GhostPost/feature_image/seo-content-marketing/https://images.unsplash.com/p
info GhostPost/feature_image/basic-on-page-seo/https://images.unsplash.com/photo
info GhostPost/feature_image/google-search-console/https://images.unsplash.com/p
info GhostPost/feature_image/link-building-techniques/https://images.unsplash.co
info GhostPost/feature_image/measure-website-speed/https://images.unsplash.com/p
info GhostPost/feature_image/schema-markup/https://images.unsplash.com/photo-150
info GhostPost/feature_image/google-analytics-tutorial/https://images.unsplash.c
info GhostPost/feature_image/create-a-wordpress-website/https://images.unsplash.
ERROR
Error processing images in node Ghost__Post__5e7057a1476ce52f8f69e194:
failed to process https://images.unsplash.com/photo-1515974256630-babc85765b1d?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f47ae251bce6e3eef1e98:
failed to process https://images.unsplash.com/photo-1505903658795-8d3cc48039e4?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6ef5d40f75eb23302d20ff:
failed to process https://images.unsplash.com/photo-1519658422992-0c8495f08389?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f1c9993de2935285c64bc:
failed to process https://images.unsplash.com/photo-1490732239438-ee956a60ed41?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f16d593de2935285c6488:
failed to process https://images.unsplash.com/photo-1492760864391-753aaae87234?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f180a93de2935285c649b:
failed to process https://images.unsplash.com/photo-1481414981591-5732874c7193?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f218d2d945b4aafa70b86:
failed to process https://images.unsplash.com/photo-1564050988016-522e96f274c6?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6ef35c0f75eb23302d20d9:
failed to process https://images.unsplash.com/photo-1529089202281-2180f7a2289c?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f197a93de2935285c64ac:
failed to process https://images.unsplash.com/photo-1511974212900-b42a18e19eb8?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f2a202d945b4aafa70ba8:
failed to process https://images.unsplash.com/photo-1521354465180-c1ceac1d709a?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f2bc52d945b4aafa70bbb:
failed to process https://images.unsplash.com/photo-1557800634-95f2a96fbd64?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f2eb62d945b4aafa70bcc:
failed to process https://images.unsplash.com/photo-1549907997-db64d6e762c3?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f30a92d945b4aafa70bde:
failed to process https://images.unsplash.com/photo-1507035895480-2b3156c31fc8?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6f203b2d945b4aafa70b71:
failed to process https://images.unsplash.com/photo-1502622796232-e88458466c33?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Post__5e6ef4cc0f75eb23302d20ec:
failed to process https://images.unsplash.com/photo-1528290869615-84fe45af6918?ixlib=rb-1.2.1&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=2000&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
success source and transform nodes - 1.881s
success building schema - 1.718s
success createPages - 0.280s
success createPagesStatefully - 0.159s
success onPreExtractQueries - 0.009s
success update schema - 0.183s
info GhostPost/feature_image/data-schema/https://images.unsplash.com/photo-15326
info GhostPage/feature_image/data-schema-page/https://images.unsplash.com/photo-
ERROR
Error processing images in node Ghost__Post__5bbafb3cb7ec4135e42fce56:
failed to process https://images.unsplash.com/photo-1532630571098-79a3d222b00d?ixlib=rb-0.3.5&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=1080&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ&s=a88235003c40468403f936719134519d
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR
Error processing images in node Ghost__Page__5bbafb3cb7ec4135e42fce57:
failed to process https://images.unsplash.com/photo-1532630571098-79a3d222b00d?ixlib=rb-0.3.5&q=80&fm=jpg&crop=entropy&cs=tinysrgb&w=1080&fit=max&ixid=eyJhcHBfaWQiOjExNzczfQ&s=a88235003c40468403f936719134519d
RequestError: getaddrinfo ENOTFOUND images.unsplash.com
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "coverImageSharp" on type "GhostSettings".
If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo.
However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/components/common/HeaderIndex.js:65:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "coverImageSharp" on type "GhostSettings".
If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo.
However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/components/common/Layout.js:124:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "coverImageSharp" on type "GhostSettings".
If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo.
However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/components/common/meta/AuthorMeta.js:106:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "coverImageSharp" on type "GhostSettings".
If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo.
However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/components/common/meta/ArticleMeta.js:180:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "coverImageSharp" on type "GhostSettings".
If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo.
However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/components/common/meta/WebsiteMeta.js:125:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "featureImageSharp" on type "GhostPost".
If you don't expect "featureImageSharp" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "featureImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "featureImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/pages/404.js:134:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "coverImageSharp" on type "GhostSettings".
If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo.
However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/components/common/SiteNav.js:86:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "featureImageSharp" on type "GhostPost".
If you don't expect "featureImageSharp" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "featureImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "featureImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/templates/index.js:145:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "featureImageSharp" on type "GhostPost".
If you don't expect "featureImageSharp" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "featureImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "featureImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/templates/author.js:140:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "featureImageSharp" on type "GhostPost".
If you don't expect "featureImageSharp" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "featureImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "featureImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/templates/post.js:227:9
ERROR #85923 GRAPHQL
There was an error in your GraphQL query:
Cannot query field "featureImageSharp" on type "GhostPost".
If you don't expect "featureImageSharp" to exist on the type "GhostPost" it is most likely a typo.
However, if you expect "featureImageSharp" to exist there are a couple of solutions to common problems:
- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "featureImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content")
It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostPost":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
File: node_modules/gatsby-theme-try-ghost/src/templates/tag.js:142:9
failed extract queries from components - 1.630s
warn The GraphQL query in the non-page component "/Users/macbook/Gatsby/g222g/no
Exported queries are only executed for Page components. It's possible you're
trying to create pages in your gatsby-node.js and that's failing for some
reason.
If the failing component(s) is a regular component and not intended to be a page
component, you generally want to use a <StaticQuery> (https://gatsbyjs.org/docs/static-query)
instead of exporting a page query.
If you're more experienced with GraphQL, you can also export GraphQL
fragments from components and compose the fragments in the Page component
query and pass data down into the child component — https://graphql.org/learn/queries/#fragments
success write out requires - 0.338s
success write out redirect data - 0.014s
success onPostBootstrap - 0.003s
⠀
info bootstrap finished - 17.352 s
⠀
success run queries - 0.081s - 26/26 322.55/s
⠀
You can now view gatsby-starter-try-ghost in the browser.
⠀
http://localhost:8000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema
⠀
http://localhost:8000/___graphql
⠀
Note that the development build is not optimized.
To create a production build, use gatsby build
⠀
success Building development bundle - 10.011s
About the pictures, I don't understand about :)
Looks like your local computer can't access pictures from unsplash. When you open a browser, and paste the following url:
ghost ls
)Hi,
Make sure ghost is actually running (the screenshot shows an inactive ghost instance).
Looks similar to https://github.com/nodejs/node/issues/5436. What node version are you running on (node -v
)?
My current node version is v12.16.1
, and then?
Okay, that's a recent version. From what I read from other threads this is most likely an node / macOS issue with looking up/caching DNS, meaning that node
cannot resolve url https://images.unsplash.com
. Thus, I don't think I can help you any further with this.
As I like this repo to be working for everyone -- what I can offer is that you put your ghost installation on a publicly reachable server and send me your content API keys, so I can run the builds myself. This would allow me to utilize more tools for debugging.
If you have another computer running on another OS, this would also be a good test in order to see if the issue has to do with your current macOS version.
Ok, I see. Will try host using Azure. Let me try it :)
Error appears when deploy Ghost from azure to the Gatsby cloud, this error log:
There was an error in your GraphQL query: Cannot query field "coverImageSharp" on type "GhostSettings". If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo. However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
There was an error in your GraphQL query: Cannot query field "coverImageSharp" on type "GhostSettings". If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo. However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
There was an error in your GraphQL query: Cannot query field "coverImageSharp" on type "GhostSettings". If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo. However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
There was an error in your GraphQL query: Cannot query field "coverImageSharp" on type "GhostSettings". If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo. However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
There was an error in your GraphQL query: Cannot query field "coverImageSharp" on type "GhostSettings". If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo. However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
There was an error in your GraphQL query: Cannot query field "coverImageSharp" on type "GhostSettings". If you don't expect "coverImageSharp" to exist on the type "GhostSettings" it is most likely a typo. However, if you expect "coverImageSharp" to exist there are a couple of solutions to common problems: - If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server - The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have - You want to optionally use your field "coverImageSharp" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add a least one entry with that field ("dummy content") It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "GhostSettings": https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
This is my content api: efe69b8bae3598864d67a13d7b Api url: https://....net
Thanks for providing a reproducible example! Problem is that you deleted the cover image in ghost admin and the repo currently cannot cope with that. I'll be working on fixing that - in the meantime please add a cover image in ghost admin and you should be good to go.
Fixed in gatsby-starter-try-ghost@1.2.5
. This version is now able to deal with empty/removed cover images.
It's great news!!! Just tried it. There is an issue on the featured image. Featured image in desktop version disappears, but in the mobile version is fine. Let me show you:
This is my repo details:
Gatsby cloud log show some issue:
(node:6700) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
The GraphQL query in the non-page component "/usr/src/app/www/node_modules/gatsby-theme-try-ghost/src/templates/page.js" will not be run.
code block or inline code language not specified in html. applying generic code block
If you need, here is content and url api:
Original issue is solved.
Hi there (again),
I just install ghost to MacBook and will pull the content to the your gatsby repo (offline). But the error appears.