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
gatsby-source-wordpress Request failed with status code 500
Your WordPress server is either overloaded or encountered a PHP error.
Error occurred while fetching nodes of the "GfEntry" type.`
Debug.log on Wordpress
[19-Dec-2024 03:53:25 UTC] PHP Notice: Undefined index: GfFieldChoice in C:\laragon\www\site\wp-content\plugins\wp-graphql\vendor\webonyx\graphql-php\src\Type\Schema.php on line 437
Error happens when I activate the WPGraphql for Gravity Form
Steps to reproduce
Wordpress PHP : 7.4.33
gatsby-source-wordpress: 7.13.5
Gravity form : 2.7.7
WPGraphQL: 1.29.3
WPGraphQL for Gravity Forms: 0.13.0.1
Need to run wordpress and gatsby
Additional context
No response
Plugin Version
0.13.0.1
Gravity Forms Version
2.7.7
WordPress Version
6.5.5
WPGraphQL Version
1.29.3
Additional enviornmental details
Running on Gatsby v5.13.7
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have disabled ALL plugins except for Gravity Forms, WPGraphQL, and WPGraphQL for Gravity Forms
Yes
My issue is with a specific 3rd-party plugin.
The text was updated successfully, but these errors were encountered:
TBH I thought gatsby-source-wordpress was abandoned. 🙈
Doesn't seem like the PHP Notice is directly related to your 500 error (both because PHP Notices don't throw a 500, and because GFFieldChoice is an object that only attaches to Form Field objects, and not GFEntry.
Additionally I recommend you follow these debugging steps: specifically trying to replicate the query first in Gatsby's Playground, and then in the WPGraphQL IDE (note: you'll need to translate those automagical Gatsby field renames to what used by vanilla GraphQL). This will both narrow down the error to a specific part of the schema as well as determine if it's a bug in gatsby-source-wordpress or something we can address here.
TBH I thought gatsby-source-wordpress was abandoned. 🙈
Doesn't seem like the PHP Notice is directly related to your 500 error (both because PHP Notices don't throw a 500, and because GFFieldChoice is an object that only attaches to Form Field objects, and not GFEntry.
Additionally I recommend you follow these debugging steps: specifically trying to replicate the query first in Gatsby's Playground, and then in the WPGraphQL IDE (note: you'll need to translate those automagical Gatsby field renames to what used by vanilla GraphQL). This will both narrow down the error to a specific part of the schema as well as determine if it's a bug in gatsby-source-wordpress or something we can address here.
Hi @justlevine , thank you for taking the time to review this. I've followed the debug steps and replicate the query for inside the WPGraphQL IDE and received this error
"debugMessage": "Return value of GraphQL\Type\Schema::getImplementations() must be an instance of GraphQL\Utils\InterfaceImplementations, null returned",
"message": "Internal server error",
"extensions": {
"category": "internal"
},
Description
Error received on Gatsby
Debug.log on Wordpress
Error happens when I activate the WPGraphql for Gravity Form
Steps to reproduce
Need to run wordpress and gatsby
Additional context
No response
Plugin Version
0.13.0.1
Gravity Forms Version
2.7.7
WordPress Version
6.5.5
WPGraphQL Version
1.29.3
Additional enviornmental details
Running on Gatsby v5.13.7
Please confirm that you have searched existing issues in the repo.
Please confirm that you have disabled ALL plugins except for Gravity Forms, WPGraphQL, and WPGraphQL for Gravity Forms
The text was updated successfully, but these errors were encountered: