Got error when upgrade WooCommerce 4.0

Having issue with wp_actionscheduler also – Have you found any solution? Thanks

Hey there!

That error message is not a full error message, so it’s a bit hard to really figure it out, but I think that’s an error with a database table not existing.

Typically that means that something happened during the update or there were some permissions errors, or something similar.

You can recreate that table manually, or you can try to run the database update again and see if that can create the table for you.

The tool to run the update is under “Status” > “Tools”

Hopefully that helps! Have a great one!

The problem is I can’t get to Status > Tools because the error blocks the WordPress Admin panel from opening if Woocommerce is activated and if it is not… well you know…

My actual error is:
2020-03-14T21:46:22+00:00 CRITICAL Uncaught Error: Cannot call abstract method ActionScheduler_Logger::init() in /home/tsadmin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBLogger.php:102
Stack trace:
#0 /home/tsadmin/public_html/wp-includes/class-wp-hook.php(286): ActionScheduler_DBLogger->init()
#1 /home/tsadmin/public_html/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array)
#2 /home/tsadmin/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#3 /home/tsadmin/public_html/wp-settings.php(523): do_action(‘init’)
#4 /home/tsadmin/public_html/wp-config.php(98): require_once(‘/home/tsadmin/p…’)
#5 /home/tsadmin/public_html/wp-load.php(37): require_once(‘/home/tsadmin/p…’)
#6 /home/tsadmin/public_html/wp-blog-header.php(13): require_once(‘/home/tsadmin/p…’)
#7 /home/tsadmin/public_html/index.php(17): require(‘/home/tsadmin/p…’)
#8 {main}
thrown in /home/tsadmin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_DBLogger.php on line 102

Thanks to all your responding,

I choose the solution is to restore the database backup which contains the 3.9.x version. I have no time to check the conflict between the plugins so it seems the best workaround for me at this time.

I will keep you guys posted if I find out something new.

Best Regards,
Duy Nguyen