Update to 6.0.1 broke my site

  • Resolved kamrafique

    (@kamrafique)


    3 years, 1 month ago

    Updating to 6.0.1 caused a fatal error in admin.
    I’ve had this before with blocks.

    I have a screenshot of the error trace but can’t seem to attach here.
    Possible conflict with AutomateWoo (this time and last time).

    How I fixed the issue:
    ftp’d to my plugin folder /wp-content/plugins/woo-gutenberg-products-block and renamed “woo-gutenberg-products-block” to “woo-gutenberg-products-blockx” then back to admin page and refresh. In my case this deactivated blocks and I used a rollback plugin to rollback back to 6.0.0 which works ok for me.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter kamrafique

    (@kamrafique)

    wp: 5.8.1
    wc: 5.6.0
    WooCommerce Blocks: 6.0.0
    AutomateWoo: 5.5.3

    2021-09-29T15:23:16+00:00 CRITICAL Uncaught Exception: Cannot construct an instance of Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry because it has not been registered. in /home/customer/www/<removed>/public_html/wp-content/plugins/woo-gutenberg-products-block/src/Registry/Container.php:89
Stack trace:
#0 /home/customer/www/<removed>/public_html/wp-content/plugins/automatewoo/admin/admin.php(56): Automattic\WooCommerce\Blocks\Registry\Container->get('Automattic\\WooC...')
#1 /home/customer/www/<removed>/public_html/wp-content/plugins/automatewoo/includes/AutomateWoo.php(159): AutomateWoo\Admin::init()
#2 /home/customer/www/<removed>/public_html/wp-includes/class-wp-hook.php(303): AutomateWoo->init('')
#3 /home/customer/www/<removed>/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array)
#4 /home/customer/www/<removed>/public_html/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#5 /home/customer/www/<removed>/public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.p in /home/customer/www/<removed>/public_html/wp-content/plugins/woo-gutenberg-products-block/src/Registry/Container.php on line 89
    • This reply was modified 3 years, 1 month ago by kamrafique.
    Plugin Support Chris Moreira – a11n

    (@chrism245)

    Hi @kamrafique!

    Thanks for reporting this!

    I have done a test on my side with WooCommerce Blocks and AutomateWoo, and I don’t receive any errors using the latest version of both extensions.

    Additionally, can you update your WooCommerce to 5.7.1, as is the latest release, and try again?

    If the problem persists, can you provide a screenshot of this error? You can paste it here, https://snipboard.io/, then send me the URL it gives to view the screenshot.

    Thread Starter kamrafique

    (@kamrafique)

    Hi @chrism245.

    I’ve updated to WC 5.7.1 and the Blocks plugin has installed successfully without error.

    Blocks 6.0.1 is now up to date and active.

    Thanks. Kam

    Plugin Support Chris Moreira – a11n

    (@chrism245)

    Glad to hear it – thanks for letting us know!

    I’ll mark this thread as resolved now. If you have any further questions, I recommend creating a new thread.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Update to 6.0.1 broke my site’ is closed to new replies.