Schema Unavailable/Missing - Can't navigate anything or query anything

[FourthElementLtd]

Description

Hi Team,

I'm struggling to understand how I cannot see the schema anymore thus creating queries isn't possible.

It is possible and the schema shows when I switch off ACF Pro, however, on a production system this obviously breaks the website.

What can I do to make sure the schema shows again?

Best regards

Darren.

Steps to reproduce

Additional context

No response

WPGraphQL Version

2.1.1

WordPress Version

6.7.2

PHP Version

7.4

Additional environment 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.

[FourthElementLtd]

Just to note, my queries are still working on the front end.

Also the Schema shows if I deactivate - WPGraphQL WooCommerce (WooGraphQL) Version 0.18.3 and ACF Pro is activated. So perhaps the issue is with WPGraphQL WooCommerce???

[justlevine]

Hey @FourthElementLtd

Please take a look at the Debugging guide: https://www.wpgraphql.com/docs/debugging , and follow the steps laid out there. My assumption is that if you turn on WP_DEBUG_LOG and GRAPHQL_DEBUG and inspect your Browser's request to the GraphQL endpoint, you'll see whatever error is preventing the schema from loading along with the trace to pinpoint the specific culprit.

schema shows when I switch off ACF Pro,
[...]
Also the Schema shows if I deactivate - WPGraphQL WooCommerce (WooGraphQL) Version 0.18.3 and ACF Pro is activated. So perhaps the issue is with WPGraphQL WooCommerce???

Indeed. If a bug only happens when external code is enabled, then there's a fairly decent change the issue is related to that codebase, and there's sadly not much we can do to fix code that exists outside our repo.

You skipped much of the issue template but from the small bit you shared, I'd hunch that one of your custom ACF fields, groups, etc is conflicting with those exposed by (WPGraphQL for) WooCommerce. Either way, I recommend following the debugging guide, and based on the results either open up an issue in the WooGraphQL or WPGraphQL for ACF repositories, or update here w. the additional information from your debugging and all the parts of GH issue template you skipped so we have enough to replicate and make this actionable.

(If you need help debugging, I strongly recommending asking for help in the WPGraphQL discord - the community is super friendly!)

PS: Marking this as invalid? doesn't imply you're not experiencing a "real" issue, only that it might not be something that we can address in the WPGraphQL core codebase.

[ajotka]

Hello!
The WP-GraphQL plugin updated automatically for me overnight and I experienced exactly the same thing. All schemas are unavailable, the frontend seems to work, but new pages throw a 500 error.

There are no errors, I checked both the graphql logs and the logs from the query monitor - empty.
The only error that is there is the console log from Apollo:

WP-GraphQL 2.1.1 (works) -> 2.3.0 (doesn't)

I don't have Woocommerce, but I have ACF Pro.
PHP 8.2
WordPress 6.7.1

[justlevine]

Hello! The WP-GraphQL plugin updated automatically for me overnight and I experienced exactly the same thing. All schemas are unavailable, the frontend seems to work, but new pages throw a 500 error.

There are no errors, I checked both the graphql logs and the logs from the query monitor - empty. The only error that is there is the console log from Apollo:

WP-GraphQL 2.1.1 (works) -> 2.3.0 (doesn't)

I don't have Woocommerce, but I have ACF Pro. PHP 8.2 WordPress 6.7.1

@ajotka your issue seems to be caused by a conflict with whatever is responsible for creating that LanguageCodeEnum and the latest version of WPGraphQL, and unrelated to whatever the OP was experiencing.

Can you please open a new bug report (with all the requested info), so we can replicate the issue and figure out the correct fix?

[chrisgrabinski]

@justlevine It looks like this is related to wp-graphql-polylang. You can replicate the error by enabling the plugin with WP-GraphQL 2.3.0 installed and enabled.

[jasonbahl]

Looks like this was resolve by WPGraphQL for PolyLang: valu-digital/wp-graphql-polylang#94