Always spinning progress in GraphiQL IDE

[odrowonz]

Description

I am using WordPress 6.2.2 and PHP FastCGI (Apache) 8.2.0 (alt). After installing release v1.14.9 and activating the plugin, I go to the GraphiQL IDE and see an endless process of progress rotation. The situation is similar when the plugin version is downgraded to 1.6.12 (I went through all the versions). Version 1.6.12 successfully opened the GraphiQL IDE for me. What could be wrong?

Steps to reproduce

1. Go to Plugins and install and activate release v1.14.9.
2. Go to GraphiQL IDE.
3. See the always spinning progress.
   

Additional context

No response

WPGraphQL Version

1.14.9

WordPress Version

6.2.2

PHP Version

FastCGI (Apache) 8.2.0 (alt)

Additional enviornment details

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have disabled ALL plugins except for WPGraphQL.

• Yes
• My issue is with compatibility with a specific WordPress plugin, and I have listed all my installed plugins (and version info) above.

[justlevine]

Hey @odrowonz

Please follow the Debugging steps. After you follow those steps, if you take a look at the Network Response, you should see a more explicit error. Once you share that we'll have a better chance of being able to help.

(Note: this plugin isn't actively tested against PHP 8.2 yet, so that could be a contributing factor).

[roenfeldt]

I second @odrowonz 's problem, the same is happening to my WordPress 6.3 installation + WPGraphQL 1.14.10.

The issue doesn't seem to be related to PHP 8.2. I tried changing the PHP version in my hosting cPanel to 8.1, 8.0, and even 7.4, but that doesn't make any difference.

The four-dots spinner won't go away, and the browser's Inspection Tools are showing a JavaScript-related error. Hopefully the attached image below will help you @jasonbahl and/or @justlevine figure out the issue.

Thank you!

[justlevine]

Hey @roenfeldt 👋

It's likely not the same bug (the IDE not loading is just a sign that there is a bug/conflict), but since @odrowonz doesn't seem to be using this ticket, I'm happy to help you debug this here in the off chance it does help the OP 😎

There's one thing missing from your screenshot that I'd need to begin: the Network Response (in your screenshot, it's on the top right of the console, the tab next to the Headers. Please make sure to turn on GraphQL debugging first 🙏).
That will show us what the server is trying to send to the GraphiQL IDE instead of the expected introspection.

[jasonbahl]

@odrowonz I attempted to reproduce on PHP 8.2 (we don't currently have automated tests for 8.2, so I thought maybe there's a chance that was the culprit) but I'm able to load GraphiQL IDE just fine on PHP 8.2

Here's the server details of the local server I set up:

And GraphiQL IDE loads fine:

There's a good chance there could be an issue with a plugin or theme you have active, so be sure to test in a clean install vs an install with many other existing plugins.

I do see that you have at least Jetpack and SpeedyCache active in your screenshot. It's important for us to know if we're dealing with an issue with WPGraphQL itself, a plugin conflict with a specific plugin / combination of plugins, or something else.

I also notice you might have WordPress set to use a different language, so there's a chance that's impacting this 🤔

[jasonbahl]

@odrowonz it looks like you're running WordPress in non-English, and if you have a custom theme active that has page templates that use non-ascii characters in the template name, there's a good chance that you're running into this issue: #2807

[jasonbahl]

@roenfeldt are you using non-ascii characters in page templates? Curious if you might also be running into #2807

[odrowonz]

Yes, I use default theme "Twenty Twenty-Three" and pages with Russian encoding.

[jasonbahl]

@odrowonz what about page templates? Like page-*.php files with Russian encoding?

If it's just page titles, that won't impact GraphiQL but page templates will.

[odrowonz]

I did an experiment. I installed standard Wordpress, and chose the English scheme, which is "Twenty Twenty-Three" by default. Then I switch the language to Russian in settings -> general. Then GraphiQL turns the hourglass - is not working. I return the language back to English. Then GraphiQL starts working . And of course all *.php files have English encoding.

[jasonbahl]

@odrowonz ok nice. This is good information. Will try to reproduce!

[justlevine]

@jasonbahl @odrowonz it sounds like #2492 - changing the locale translates the WP template name (#2807 is just a manual subset of the same issue).

[odrowonz]

Colleagues, is there any deadline for fixing this bug?

[justlevine]

@odrowonz assuming your issue is the same as the ones I linked previously (and if so, please let us know so we can consolidate the tickets 🙏), then you can try #2808 and see if it resolves your issue.

That particular PR needs feedback and unit testing before it can be merged, and if it doesn't solve things for you then we likely need a separate fix. Either way, contributions are always welcome!

[odrowonz]

@odrowonz assuming your issue is the same as the ones I linked previously (and if so, please let us know so we can consolidate the tickets 🙏), then you can try #2808 and see if it resolves your issue.

That particular PR needs feedback and unit testing before it can be merged, and if it doesn't solve things for you then we likely need a separate fix. Either way, contributions are always welcome!

Is there any release that includes this edit? (I tried 1.14.10 and it doesn't work there yet)

[odrowonz]

Can you compile pre-release for test?

[justlevine]

@odrowonz

assuming your issue is the same as the #2881 (comment) (and if so, please let us know so we can consolidate the tickets 🙏),

You seemed to miss ☝️ part of my last reply, but from your responses I'm going to assume that you read that issue and it is a duplicate of this one. As such, I'm closing this in favor of #2492 (if I'm wrong, let us know and we'll reopen).

Is there any release that includes this edit? (I tried 1.14.10 and it doesn't work there yet)

Like I said, that particular PR needs feedback and unit testing before it can be merged.

Can you compile pre-release for test?

To "compile" that or any branch, you can pull / download it locally, and then run composer install --no-dev --optimize-autoloader from inside the plugin folder. (or just composer install if you want to include the dev-deps needed to contribute).