Tim Vollmer

@lydiarose It’s a good reminder for people like me who are a little lazy to make sure you do a backup before updating plugins, even if they’re a big trustworthy one like WooCommerce. I really feel for anyone who doesn’t have the old plugin files handy to restore things when a buggy update causes major problems.

I’m not sure what the cause is, although my speculation is that something in the new WooCommerce 3.6.1 update is clashing with the WooCommerce Blocks plugin.

My solution was to delete the new WooCommerce files and replace with my previous backup. Site is working normally again. I think I’m going to wait a little while for the bugs to get ironed out before I update it again.

Thanks for all your help @t-p. I think I’ve got there. The site appears to be running properly now. Fingers crossed!

@t-p, thanks for that detailed response.
I have followed those instructions. None of those deactivations or name changes have resolved the issue. Currently, all plugins are still deactivated, my .htaccess file is renamed, and the theme is disabled. The error message that is being logged is below. The error log is cPanel isn’t listing any errors. Where else should I look for more detailed error information?

[09-Dec-2018 04:59:02 UTC] PHP Fatal error: Uncaught Error: Class ‘WP_Roles’ not found in /home/canyonge/public_html/wp-settings.php:383
Stack trace:
#0 /home/canyonge/public_html/wp-config.php(101): require_once()
#1 /home/canyonge/public_html/wp-load.php(37): require_once(‘/home/canyonge/…’)
#2 /home/canyonge/public_html/wp-blog-header.php(13): require_once(‘/home/canyonge/…’)
#3 /home/canyonge/public_html/index.php(17): require(‘/home/canyonge/…’)
#4 {main}
thrown in /home/canyonge/public_html/wp-settings.php on line 383