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
Currently, if GRAPHQL_JWT_AUTH_SECRET_KEY is not set in wp-config.php it causes an internal server error with WPGraphQL and prevents the schema from loading.
Failing to add the key in wp-config.php should present an error in the admin and probably not disable the schema.
The text was updated successfully, but these errors were encountered:
Of note: there's also the filter graphql_jwt_auth_secret_key. I propose the plugin, by default, should use a filter that returns the constant SECURE_AUTH_KEY. Would be as secure as the WordPress install itself and would allow the plugin to "work out of the box" while still allowing for custom keys set in functions and wp-config.
Currently, if GRAPHQL_JWT_AUTH_SECRET_KEY is not set in
wp-config.php
it causes an internal server error with WPGraphQL and prevents the schema from loading.Failing to add the key in
wp-config.php
should present an error in the admin and probably not disable the schema.The text was updated successfully, but these errors were encountered: