-
Notifications
You must be signed in to change notification settings - Fork 13
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
"gatsby-source-craft" threw an error while running the sourceNodes lifecycle #50
Comments
This is most likely due to the Tags plugin by Ether Creative. I'm not sure what their plans are regarding GraphQL support for the enhanced Tag element the plugin provides, but, at the very least, until they add that support and provide a Gatsby integration, the plugin should let Gatsby know that their element type should be excluded from updates. I've opened a new issue in their repository for this. (ethercreative/tags#20) |
@mmorkt can you update Tags plugin to 1.0.9 and check if the issue is resolved? |
We reactivated the seccond site and installed Tags 1.0.9, but it didn't help, we are getting the same error. We tried: |
@mmorkt Can you check Craft logs for this, please? There should be an error that occurs during the GraphQL request to fetch updated content information. |
@andris-sevcenko This is the error from web.log
|
@andreasottosson @mmorkt ah okay. I see how I can be more defensive against this. I'm curios, though, how this might have happened. Seems like the data is a bit messed up there - there is an updated element but it has incomplete information. Is it possible for you to send over the If this is possible, can you, please, send it over to [email protected] and mention this GH issue? Thank you! |
@andris-sevcenko of course! I have sent it via e-mail now. Sorry, it's 18.000+ lines 😬 This is probably some weird edge case, if we clone the site and run it locally in containers (Craft official docker image) this problem goes away. And also as mentioned if we disable "multisite". One thing to know is that we have had "Formie" installed on this site and that caused a lot of other GQL related errors. Don't know if they are related though. Have a nice weekend! |
Description
I'm getting this error when running two sites with diffrent URL’s. The main site should be headless, the second site got some minor functions where I’m using Crafts CMS' templating engine.
After setting up the second site my GatsbyJS site wont build anymore and I’m getting this error. The only workaround so far is to run “garsby clean”. after making an update or changes on entries.
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: