search

pristas-peter / wp-graphql-gutenberg

Query gutenberg blocks with wp-graphql
https://wp-graphql-gutenberg.netlify.app
GNU General Public License v3.0
301 stars 62 forks source link

Fatal error: Uncaught WPGraphQLGutenberg\Blocks\RegistryNotSourcedException: Client side block registry is missing. You need to open up gutenberg or load it from WPGraphQLGutenberg Admin page. #130

Open jakubszynklarz opened 2 years ago

jakubszynklarz commented 2 years ago

Hello, after installing the latest version of the wp graphql gutenberg plugin, an error occurred below - after disabling the plugin, the error disappears.

Fatal error: Uncaught WPGraphQLGutenberg\Blocks\RegistryNotSourcedException: Client side block registry is missing. You need to open up gutenberg or load it from WPGraphQLGutenberg Admin page. in /usr/home/*****/domains/*****/public_html/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Blocks/Registry.php:41 Stack trace: #0 /usr/home/*****/domains/*****/public_html/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Schema/Types/BlockTypes.php(263): WPGraphQLGutenberg\Blocks\Registry::get_registry() #1 /usr/home/*****/domains/*****/public_html/wp-includes/class-wp-hook.php(303): WPGraphQLGutenberg\Schema\Types\BlockTypes->WPGraphQLGutenberg\Schema\Types\{closure}(Object(WPGraphQL\Registry\TypeRegistry)) #2 /usr/home/*****/domains/*****/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #3 /usr/home/*****/domains/*****/public_html/wp-includes/plugin.php(470): WP_Hook->do_actio in /usr/home/*****/domains/*****/public_html/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Blocks/Registry.php on line 41

PHP 7.3.31 WP 5.8.2

PLUGINS:

Does anyone know what is the cause of the error?

jakubszynklarz commented 2 years ago

@pristas-peter @jasonbahl are you able to help solve the problem?

pristas-peter commented 2 years ago

Client side block registry is missing. You need to open up gutenberg or load it from WPGraphQLGutenberg Admin page.

jakubszynklarz commented 2 years ago

@pristas-peter There is no such possibility, an error occurs.

error

jakubszynklarz commented 2 years ago

@pristas-peter @jasonbahl are you able to help solve the problem?

jasonbahl commented 2 years ago

@jakubszynklarz Can you try with only WPGraphQL and WPGraphQL for Gutenberg active?

If it's still failing, can you confirm that you have any public post types that are using Gutenberg? And no plugins/code snippets that are disabling the block editor?

If it succeeds with only WPGraphQL + WPGraphQL for Gutenberg, I'd suggest activating the other plugins one at a time and updating the block registry to see which plugin might be causing a conflict.

For what it's worth, I didn't experience this issue with just WPGraphQL and WPGraphQL for Gutenberg active.

jakubszynklarz commented 2 years ago

@jasonbahl Unfortunately, despite disabling all plugins and leaving WpGraphql and GraphQL Gutenberg enabled, I still get the same error

williamegomezo commented 2 years ago

Any update on this? Getting same error when run this plugin on docker image

steinbergh commented 2 years ago

I Have Gutenberg restricted to all but one custom post type (im using ACF everywhere else) would this be causing this issue cause ive run into this as well

jakubszynklarz commented 2 years ago

@pristas-peter, @jasonbahl Will you suggest a solution? I noticed that after clicking button update blocks it throws an error in the browser console, the address /wp-graphql-gutenberg/v1/block-registry?Locale=user -> error 403

The problem appeared when I started building another project on the WP updated to version 5.8.2+. In another project where the WP version is 5.7.6 everything works fine.

jakubszynklarz commented 2 years ago

@pristas-peter @jasonbahl I managed to register the blocks, but the error below still occurs

Fatal error: Uncaught WPGraphQLGutenberg\Blocks\RegistryNotSourcedException: Client side block registry is missing. You need to open up gutenberg or load it from WPGraphQLGutenberg Admin page. in /usr/home/*****/domains/*****/public_html/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Blocks/Registry.php:41 Stack trace: #0 /usr/home/*****/domains/*****/public_html/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Schema/Types/BlockTypes.php(263): WPGraphQLGutenberg\Blocks\Registry::get_registry() #1 /usr/home/*****/domains/*****/public_html/wp-includes/class-wp-hook.php(303): WPGraphQLGutenberg\Schema\Types\BlockTypes->WPGraphQLGutenberg\Schema\Types\{closure}(Object(WPGraphQL\Registry\TypeRegistry)) #2 /usr/home/*****/domains/*****/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #3 /usr/home/*****/domains/*****/public_html/wp-includes/plugin.php(470): WP_Hook->do_actio in /usr/home/*****/domains/*****/public_html/wp-content/plugins/wp-graphql-gutenberg-0.3.11/src/Blocks/Registry.php on line 41

codedbyglenden commented 2 months ago

I know this is a really old ticket. But for anyone running into this, I fixed it by enabling rest on a post-type, and visiting the post-new.php file for that post-type. For example with the page post type this would be:

${your-domain}/wp-admin/post-new.php?post_type=page

You only need to visit it once & the error will be gone.