Hi @rughooker. That’s awful! We definitely don’t want any release of Woo Blocks breaking people’s sites and spend a lot of effort and time testing before release to try to avoid that.
Are you be able to share any more additional details about what was broken on your site? Were there any error messages in your PHP logs?
I can:
Fatal error: Uncaught Exception: Cannot construct an instance of Automattic\WooCommerce\Blocks\StoreApi\SchemaController because it has not been registered. in /home/customer/www/pogonotrophics.com/public_html/wp-content/plugins/woo-gutenberg-products-block/src/Registry/Container.php:89 Stack trace: #0 /home/customer/www/pogonotrophics.com/public_html/wp-content/plugins/woocommerce-subscriptions/includes/class-wc-subscriptions-extend-store-endpoint.php(47): Automattic\WooCommerce\Blocks\Registry\Container->get('Automattic\\WooC...') #1 /home/customer/www/pogonotrophics.com/public_html/wp-includes/class-wp-hook.php(303): WC_Subscriptions_Extend_Store_Endpoint::init('') #2 /home/customer/www/pogonotrophics.com/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #3 /home/customer/www/pogonotrophics.com/public_html/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #4 /home/customer/www/pogonotrophics.com/public_html/wp-content/plugins/woo-gutenberg-products-block/src/Domain/Bootstrap.php(6 in /home/customer/www/pogonotrophics.com/public_html/wp-content/plugins/woo-gutenberg-products-block/src/Registry/Container.php on line 89
That would be absolutely impossible as I cannot access the site. Even in safe mode, it seems as soon as I restore a back up Blocks auto updates before I can even get in to turn updates off. Working with a tech, trying to get some level of functionality.
Can you reach out to your hosting support? This issue is coming from both WooCommerce Subscriptions and WooCommerce Blocks. We suspect it might be an object cache issue, which only your hosting support can clear for you.
Both WooCommerce Subscriptions and WooCommerce Blocks got new versions. When both are at latest version, there is this error. I can also reproduce it. So problem is definitely with your plugins, I cannot investigate what change caused this.
If it helps, WooCommerce 5.6.0 is active where I reproduced it. In another thread, it was reported that error is gone when WooCommerce is updated to the latest version. I cannot try that at the moment, but in any case you should fix this bug.
I just deactivated the plug-in. No more automatic trusting of big name plug-ins. I guess I’ve lost my innocence.
Thanks Milan, thanks for providing an update here.
While you are somewhat correct, we have traced the issue to a combination of:
– WooCommerce blocks requires the latest version of WooCommerce Core (see the announcement made earlier in the summer here
– We had code in WooCommerce Blocks that was still executing an action extensions were using to validate the WooCommerce Blocks feature plugin was fully loaded when in fact it was paused because of incorrect version support on the related site. This in turn caused those extensions to throw a fatal PHP error because they were depending on code that should be loaded when in fact it was not.
We are readying a fix that should be released relatively shortly that will address the fatal error, but users will still need to be on the latest version of WooCommerce in order to use the WooCommerce Blocks plugin and its features.
Thank you everyone for your reports, we released 6.0.2 which should fix this.
