imranhsayed / gatsby-wordpress-themes Goto Github PK

Hi :)

Had no problems 1 week earlier while running your theme, but since today I can't quite make it work.
It keeps crashing when creating the pages.

I have these 2 errors :
Cannot query field "content" on type "hwgraphql_Page".
gatsby-wordpress-theme-phoenix threw an error while running the createPages lifecycle

And I didn't change anything...

This theme is awesome by the way ! Can't wait to make my way through it !

Kind regards,
Prisca

Running npm run develop and getting this error any idea's where I've gone wrong

ERROR #98123 WEBPACK

Generating development JavaScript bundle failed

            border: 1px solid $gray-300;
               ^
  Undefined variable: "$gray-300".
  in C:\VS\my-gatsby-project\node_modules\@wordpress\block-library\src\calendar\style.scss (line 7, column 21)

File: node_modules\gatsby-wordpress-theme-phoenix\src\components\home\feature-posts\style.scss

I am getting this error when activating headless-cms plugin, can you please take look at it?
My set up, Wordpress 5.4.2, PHP 7.4.7 running locally using Laragon.

Plugin could not be activated because it triggered a fatal error.

Fatal error: Uncaught Error: Class 'Headless_CMS\Features\Inc\Plugin' not found in C:\Utilities\laragon\www\smrwp\wp-content\plugins\headless-cms\headless-cms.php:33 Stack trace: #0 C:\Utilities\laragon\www\smrwp\wp-content\plugins\headless-cms\headless-cms.php(36): headless_cms_features_plugin_loader() #1 C:\Utilities\laragon\www\smrwp\wp-admin\includes\plugin.php(2255): include('C:\Utilities\la...') #2 C:\Utilities\laragon\www\smrwp\wp-admin\plugins.php(177): plugin_sandbox_scrape('headless-cms/he...') #3 {main} thrown in C:\Utilities\laragon\www\smrwp\wp-content\plugins\headless-cms\headless-cms.php on line 33

TypeError: _props$pageContext.page is null
FrontPage
node_modules/gatsby-wordpress-theme-phoenix/src/templates/front-page/index.js:10

This is shown at the browser (no error at gatsby server).
It seems that the wordpress content is not properly set.

Regarding point 6 of installation:
6 - Add the ACF required data on the Home page from WordPress Dashboard.
This is not much precise. I've setup main page, menus and some posts, but something could be missing.

In order to check what the problem is, I think it would be fine if you can provide a backup of your wordpress demo site (posts, pages, images, etc.) so we can reproduce exactly your site for testing.

Thx

Are these warnings something to be concerned about?

You can now viewosite in the browser.
⠀
  http://localhost:8000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema
⠀ Building development bundle
  http://localhost:8000/___graphql
⠀
Note that the development build is not optimized.
To create a production build, use gatsby build
⠀
warn ESLintError: 
C:\dev\gatsby-wordpress-themes\packages\gatsby-wordpress-theme-phoenix\src\components\footer\index.js
  30:8   warning  'socialIcons' is assigned a value but never used
                   no-unused-vars
  74:42  warning  Using target="_blank" without rel="noreferrer" is a security risk: see
https://html.spec.whatwg.org/multipage/links.html#link-type-noopener  react/jsx-no-target-blank

warniESLintError:
C:\dev\gatsby-wordpress-themes\packages\gatsby-wordpress-theme-phoenix\src\components\home\client-search\index.js
  126:13  warning  'posts' is assigned a value but never used  no-unused-vars

✖ 1 problem (0 errors, 1 warning)

warniESLintError:
C:\dev\gatsby-wordpress-themes\packages\gatsby-wordpress-theme-phoenix\src\components\home\search\index.js
  7:8  warning  'SearchBackgroundImg' is defined but never used  no-unused-vars

✖ 1 problem (0 errors, 1 warning)

warniESLintError:
C:\dev\gatsby-wordpress-themes\packages\gatsby-wordpress-theme-phoenix\src\components\page\index.js
   3:8  warning  'Img' is defined but never used               no-unused-vars
  13:8  warning  'imgData' is assigned a value but never used  no-unused-vars

✖ 2 problems (0 errors, 2 warnings)

success Building development bundle - 12.703s

So I understand Gatsby is a way to make a WordPress site static....

However, this doesn't make things easier for a bootstrap developer to design unless he know React....

So, My question is....

Isn't it much easier to "Just" make one custom meta field call HTML, and do a site scrap to custom meta field on publish.
This will store static content of the page into an custom meta field.
Then load the static content into a REACT headless WordPress BLANK theme.
This will also allow the user to add whatever plugin s/he wants, because the resulted output is static html.

Would that work better?

Generating development JavaScript bundle failed
border: 1px solid $gray-200;
^
Undefined variable: "$gray-200".
in /home/dean/projects/tutorials/phoenix/node_modules/@wordpress/block-library/src/calendar/style.scss (line 7, column 21)

File: node_modules/gatsby-wordpress-theme-phoenix/src/components/header/style.scss

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 } ) => {

10 | await createAllPages( { actions, graphql } );
| ^
11 | await createAllPosts( { actions, graphql } );
12 | await createFrontPage( { actions, graphql } );
13 | await createBlogPage( { actions, graphql } );

File: ../packages/gatsby-wordpress-theme-phoenix/gatsby-node.js:10:2

Hi there, my question is as the title, does this theme work with WooCommerce?

I am receiving below error when running : 'npm run develop' , specifically
Cannot query field "altText" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".
and
error Generating development JavaScript bundle failed

encinoe@web:~/my-gatsby-project$ npm run develop

[email protected] develop /home/encino-emergency-dentist.com/my-gatsby-project
gatsby develop

success open and validate gatsby-configs - 0.041s
success load plugins - 1.801s
success onPreInit - 0.118s
success initialize cache - 0.020s
success copy gatsby files - 0.089s
success onPreBootstrap - 0.031s
success createSchemaCustomization - 0.027s
success Checking for changed pages - 0.003s
success source and transform nodes - 7.512s
Found schema 'hwgraphql', traversing for fields with name 'sourceUrl'
success building schema - 1.759s
error There was an error in your GraphQL query:

Cannot query field "altText" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".

If you don't expect "altText" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "altText" 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 "altText" 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 at 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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error There was an error in your GraphQL query:

Cannot query field "sourceUrl" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".

If you don't expect "sourceUrl" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "sourceUrl" 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 "sourceUrl" 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 at 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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error There was an error in your GraphQL query:

Cannot query field "sourceUrlSharp" on type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge".

If you don't expect "sourceUrlSharp" to exist on the type "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge" it is most likely a typo.
However, if you expect "sourceUrlSharp" 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 "sourceUrlSharp" 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 at 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 "hwgraphql_NodeWithFeaturedImageToMediaItemConnectionEdge":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error "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 } ) => {

10 | await createAllPages( { actions, graphql } );
| ^
11 | await createAllPosts( { actions, graphql } );
12 | await createFrontPage( { actions, graphql } );
13 | await createBlogPage( { actions, graphql } );

TypeError: Cannot read property 'HWGraphQL' of undefined

• pages.js:64
  [my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/create-pages/pages.js:64:50

• pages.js:61 fetchPosts
  [my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/create-pages/pages.js:61:10

• pages.js:71 module.exports
  [my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/create-pages/pages.js:71:2

• gatsby-node.js:10 Object.exports.createPages
  [my-gatsby-project]/[gatsby-wordpress-theme-phoenix]/gatsby-node.js:10:2

• api-runner-node.js:460 runAPI
  [my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:460:16

• From previous event:

• api-runner-node.js:589 Promise.catch.decorateEvent.pluginName
  [my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:589:9

• From previous event:

• api-runner-node.js:588
  [my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:588:14

• timers.js:461 processImmediate
  internal/timers.js:461:21

• From previous event:

• api-runner-node.js:561
  [my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:561:13

• From previous event:

• api-runner-node.js:477 module.exports
  [my-gatsby-project]/[gatsby]/src/utils/api-runner-node.js:477:3

• create-pages.ts:25 createPages
  [my-gatsby-project]/[gatsby]/src/services/create-pages.ts:25:9

• interpreter.js:722 Interpreter.exec
  [my-gatsby-project]/[xstate]/lib/interpreter.js:722:27

• interpreter.js:204 Interpreter.execute
  [my-gatsby-project]/[xstate]/lib/interpreter.js:204:22

• interpreter.js:224 Interpreter.update
  [my-gatsby-project]/[xstate]/lib/interpreter.js:224:18

• interpreter.js:125
  [my-gatsby-project]/[xstate]/lib/interpreter.js:125:23

• scheduler.js:60 Scheduler.process
  [my-gatsby-project]/[xstate]/lib/scheduler.js:60:13

• scheduler.js:44 Scheduler.schedule
  [my-gatsby-project]/[xstate]/lib/scheduler.js:44:14

• interpreter.js:121 Interpreter.send
  [my-gatsby-project]/[xstate]/lib/interpreter.js:121:29

• interpreter.js:840 actor.id
  [my-gatsby-project]/[xstate]/lib/interpreter.js:840:23

info Total nodes: 66, SitePage nodes: 1 (use --verbose for breakdown)
failed createPages - 0.457s
success Checking for changed pages - 0.001s
success createPagesStatefully - 0.141s
success update schema - 0.031s
success write out redirect data - 0.002s
success Build manifest and related icons - 0.173s
success onPostBootstrap - 0.176s
info bootstrap finished - 20.418s
success onPreExtractQueries - 0.001s
success extract queries from components - 1.035s
success write out requires - 0.203s
success run static queries - 0.824s - 2/2 2.43/s
success run page queries - 0.022s - 1/1 45.43/s
error Generating development JavaScript bundle failed

            **width: calc(25% - #{ $button-margin });**
                                   ^
  Undefined variable: "$button-margin".
  in /home/encino-emergency-dentist.com/my-gatsby-project/node_modules/@wordpress/block-library/src/button/style.scss (line 46, column 41)

error Generating development JavaScript bundle failed

            width: calc(25% - #{ $button-margin });
                                   ^
  Undefined variable: "$button-margin".
  in /home/encino-emergency-dentist.com/my-gatsby-project/node_modules/@wordpress/block-library/src/button/style.scss (line 46, column 41)

error Generating development JavaScript bundle failed

            width: calc(25% - #{ $button-margin });
                                   ^
  Undefined variable: "$button-margin".
  in /home/encino-emergency-dentist.com/my-gatsby-project/node_modules/@wordpress/block-library/src/button/style.scss (line 46, column 41)

failed Building development bundle - 13.442s

wp-graphiql is listed as a dependency on README but this is deprecated now:

https://github.com/wp-graphql/wp-graphiql