Hi @ladysyren,
The WC update broke this site
I’m sorry to learn about this. Could you please share more details so we’re able to help you troubleshoot and fix this as soon as possible? How did it break the site? Which error are you getting? Where do you see the error? When visiting which page or setting, or performing which action?
Please also share with us the necessary information below for us to investigate the issue further:
- Fatal error logs (if any) under WooCommerce > Status > Logs.
You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.
Once we have more information, we’ll be able to assist you further.
Thanks!
-OP
It created a fatal error and no one could access the site. I had to login to the CPANEL to rename the plugin and all associated with it just to access the site and the site’s admin dashboard. My client is using the legacy API for the Printify to WooCommerce plugin. And, my client needs to be able to accept payments for a booking system that uses WooCommerce.
I’m unable to get to the WooCommerce – Status – Logs so I can’t get that info.
I was able to get this:
Error Details
=============
An error of type E_ERROR was caused in line 19 of the file /home/XXXXXXX/public_html/wp-content/plugins/woocommerce/includes/class-wc-api.php. Error message: Uncaught Error: Class "WC_Legacy_API" not found in /home/XXXXXXX/public_html/wp-content/plugins/woocommerce/includes/class-wc-api.php:19
Stack trace:
#0 /home/XXXXXXX/public_html/wp-content/plugins/woocommerce/includes/class-wc-autoloader.php(54): include_once()
#1 /home/XXXXXXX/public_html/wp-content/plugins/woocommerce/includes/class-wc-autoloader.php(98): WC_Autoloader->load_file('/home/XXXXXXX/...')
#2 [internal function]: WC_Autoloader->autoload('wc_api')
#3 /home/XXXXXXX/public_html/wp-content/plugins/woocommerce-legacy-rest-api/includes/class-wc-legacy-rest-api-plugin.php(146): class_exists('WC_API')
#4 /home/XXXXXXX/public_html/wp-content/plugins/woocommerce-legacy-rest-api/includes/class-wc-legacy-rest-api-plugin.php(19): WC_Legacy_REST_API_Plugin::legacy_api_still_in_woocommerce()
#5 /home/XXXXXXX/public_html/wp-includes/class-wp-hook.php(324): WC_Legacy_REST_API_Plugin::on_woocommerce_init('')
#6 /home/XXXXXXX/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
#7 /home/XXXXXXX/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#8 /home/XXXXXXX/public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php(800): do_action('woocommerce_ini...')
#9 /home/XXXXXXX/public_html/wp-includes/class-wp-hook.php(324): WooCommerce->init('')
#10 /home/XXXXXXX/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#11 /home/XXXXXXX/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/XXXXXXX/public_html/wp-settings.php(695): do_action('init')
#13 /home/XXXXXXX/public_html/wp-config.php(98): require_once('/home/XXXXXXX/...')
#14 /home/XXXXXXX/public_html/wp-load.php(50): require_once('/home/XXXXXXX/...')
#15 /home/XXXXXXX/public_html/wp-admin/admin.php(34): require_once('/home/XXXXXXX/...')
#16 /home/XXXXXXX/public_html/wp-admin/index.php(10): require_once('/home/XXXXXXX/...')
#17 {main}
thrown
Hi @ladysyren
From what I gather, looking at the logs shared here, you have updated to WooCommerce version 9.0.0.
Note: As of WooCommerce 9.0.x, you need to install https://wordpress.org/plugins/woocommerce-legacy-rest-api/
This has been reported on GitHub (direct link), and there is a workaround linked here. (another way to apply the workaround is the one @camosystems shared above — thanks for chiming in!)
I trust that points you in the right direction, but if you have more questions, let us know.
We’re happy to help.
Plugin Author
Barry
(@barryhughes-1)
@ladysyren even if you can’t share information from your system status report, it could be really useful for us to know who your web host is (if you are happy to share that information)? Thank you!
Hi there 👋 ,
We haven’t heard from you in a while; I trust you’ve been able to update to 9.0.1 where this was fixed or above.
Feel free to start a new thread if you have any more questions.
Thanks!
-OP
