Title: WooCommerce causing critical error Last modified: September 9, 2021 --- # WooCommerce causing critical error * Resolved [annemadejewelry](https://wordpress.org/support/users/annemadejewelry/) * (@annemadejewelry) * [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/) * Hi, I have been using Woocommerce successfully for years, along with several other plugins. Recently my site went down with a note: “There has been a critical error on this website. Please check your site admin email inbox for instructions.” I clicked the associated link to troubleshoot. * I disabled all of my plugins using phpMyAdmin on GoDaddy (host), then activated only WooCommerce and got the same critical error. * I disabled plugins again, changed my theme from Boutique (by WooCommerce) to Twenty Nineteen, and got the same error after reactivating Woocommerce. * Plugins and themes are all up to date, and I am running WordPress version 5.8 and the latest php version that GoDaddy offers (7.3). * What should I do? Thank you for your help! * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fwoocommerce-causing-critical-error-2%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Support [abwaita a11n](https://wordpress.org/support/users/abwaita/) * (@abwaita) * [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/#post-14857528) * Hi [@annemadejewelry](https://wordpress.org/support/users/annemadejewelry/), * As per our [server recommendations](https://docs.woocommerce.com/document/server-requirements/), WooCommerce requires PHP 7.4 and above to run smoothly. This might be the issue causing the critical error. * Nonetheless, we’d like to view the full fatal error log. Kindly check if you can find it in any of the locations stated in this guide – [https://docs.woocommerce.com/document/finding-php-error-logs/](https://docs.woocommerce.com/document/finding-php-error-logs/). * Thanks. * Thread Starter [annemadejewelry](https://wordpress.org/support/users/annemadejewelry/) * (@annemadejewelry) * [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/#post-14858964) * Hi! Thanks for taking the time to reply. * I can’t access any of the WooCommerce menu when it is deactivated, and when it is activated it takes the whole site down with it and I can’t access the dashboard. I tried unsuccessfully to find an error/debug log on the server, but did enable debugging and got this report after activating WooCommerce: * ``` Warning: include_once(/var/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php): failed to open stream: No such file or directory in /var/www/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 509 Warning: include_once(): Failed opening '/var/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php' for inclusion (include_path='.:/opt/remi/php73/root/usr/share/pear:/opt/remi/php73/root/usr/share/php:/usr/share/pear:/usr/share/php') in /var/www/wp-content/plugins/woocommerce/includes/class-woocommerce.php on line 509 Warning: require(/var/www/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Package.php): failed to open stream: No such file or directory in /var/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 87 Fatal error: require(): Failed opening required '/var/www/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/Package.php' (include_path='.:/opt/remi/php73/root/usr/share/pear:/opt/remi/php73/root/usr/share/php:/usr/share/pear:/usr/share/php') in /var/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 87 Notice: is_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/wp-includes/functions.php on line 5535 Notice: is_singular was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/wp-includes/functions.php on line 5535 Notice: is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/wp-includes/functions.php on line 5535 Notice: is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/www/wp-includes/functions.php on line 5535 ``` * Thank you, [@abwaita](https://wordpress.org/support/users/abwaita/) ! * [MayKato](https://wordpress.org/support/users/maykato/) * (@maykato) * [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/#post-14862557) * Hi [@annemadejewelry](https://wordpress.org/support/users/annemadejewelry/) * It looks like there are some missing files. Can you manually deactivate the WooCommerce plugin via FTP, and then reinstall it from [https://wordpress.org/plugins/woocommerce/](https://wordpress.org/plugins/woocommerce/)? If you are not familiar with FTP, you can contact GoDaddy for assistance – they should be able to help you. * Here is a great tutorial on how to manually disable plugins: [https://kinsta.com/knowledgebase/disable-wordpress-plugins/#how-to-disable-wordpress-plugins-via-ftp](https://kinsta.com/knowledgebase/disable-wordpress-plugins/#how-to-disable-wordpress-plugins-via-ftp) * Thread Starter [annemadejewelry](https://wordpress.org/support/users/annemadejewelry/) * (@annemadejewelry) * [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/#post-14866360) * That worked! Thank you, [@maykato](https://wordpress.org/support/users/maykato/)! Each time the critical error happened I was able to deactivate all plugins using phpMyAdmin via Godaddy, so I was able to delete the deactivated WooCommerce plugin from the dashboard, no FTP needed. * It’s requesting a WooCommerce database update, so I’m doing a site backup first. And then I’m hoping to go back to what I know, which is making jewelry. Thank you for your patience and willingness to help people like me, [@maykato](https://wordpress.org/support/users/maykato/) and [@abwaita](https://wordpress.org/support/users/abwaita/) ! * [Mirko P.](https://wordpress.org/support/users/rainfallnixfig/) * (@rainfallnixfig) * [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/#post-14868010) * Hi [@annemadejewelry](https://wordpress.org/support/users/annemadejewelry/), * Glad to hear that [@maykato](https://wordpress.org/support/users/maykato/)’s suggestion was helpful! Now that the issue is resolved, feel free to create a new topic if you need assistance with anything else. * Cheers. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘WooCommerce causing critical error’ is closed to new replies. * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504) * [WooCommerce](https://wordpress.org/plugins/woocommerce/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/) * 5 replies * 3 participants * Last reply from: [Mirko P.](https://wordpress.org/support/users/rainfallnixfig/) * Last activity: [4 years, 8 months ago](https://wordpress.org/support/topic/woocommerce-causing-critical-error-2/#post-14868010) * Status: resolved