Closed delasign closed 1 year ago
Hi, thanks for reporting! I raised a PR to improve this behaviour.
Thanks @i-just, I saw the PR was merged - how do I get it into my project ?
Gatsby Helper 1.1.4 (Craft 3) and 2.0.2 (Craft 4) were just released wit the fix. Thanks again!
Just confirmed the fix works on both the GraphiQL and on Gatsby. Thanks @i-just @brandonkelly !
What happened?
A node changes call produces an internal server error:
GraphQL Call:
Description
I noticed an error with your GraphQL that is causing my system to break.
I initially thought it was exclusive to the gatsby-source-craft plugin but it turns out it also causes an internal server error in the CraftCMS GraphQL.
The issue is detailed here: https://github.com/craftcms/gatsby-source-craft/issues/114
Please note that the Private Schema does not have access to subscribers default entries.
If I use the "Full Schema" this issue dissapears
Steps to reproduce
Expected behavior
I believe that the expected behavior is it should not find updated nodes outside of the schema.
Actual behavior
Please note that the Private Schema does not have access to subscribers default entries.
Craft CMS version
4.4.17
PHP version
8.0.28
Operating system and version
No response
Database type and version
No response
Image driver and version
No response
Installed plugins and versions
Amazon S3 | 2.0.3 Field Manager | 3.0.6 Mail Service (Custom, Non Released Plugin) | 1.0.0 Redactor | 3.0.4 Remote Sync | 4.1.1 Super Table | 3.0.9 Gatsby Helper | 2.0.1