Recovery Mode: mentions these errors

The WooCommerce version I am having some trouble with is 8.2.2.
The main issue is switching between PHP 8.1 and 8.0 and how it affects multiple plugins. As there are a few plugins that were active with PHP 8.1 then deactivated and reactivated with PHP 8.0 causing errors.

Another fatal error. Using theme Enfold.

WordPress version 6.4.1

Active theme: Enfold (version 5.6.8)

Current plugin: WooCommerce (version 8.2.2)

PHP version 8.1.13

Error Details

=============

An error of type E_ERROR was caused in line 57 of the file /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php. Error message: Uncaught Error: Failed opening required '/home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php:57

Stack trace:

#0 /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_Versions.php(59): action_scheduler_initialize_3_dot_6_dot_3()

#1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(322): ActionScheduler_Versions::initialize_latest_version()

#2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action()

#4 /home/L/labhusetno/www/wp-settings.php(506): do_action()

#5 /home/L/labhusetno/www/wp-config.php(96): require_once('/home/L/labhuse...')

#6 /home/L/labhusetno/www/wp-load.php(50): require_once('/home/L/labhuse...')

#7 /home/L/labhusetno/www/wp-admin/admin-ajax.php(22): require_once('/home/L/labhuse...')

#8 {main}

 thrown

I went ahead and made a new video showing problems going from PHP 8.1 to PHP 8.0.

Looking at the WooCommerce -> Status -> Logs I see a lot of errors for each day. Here are some additional errors related to WooCommerce.

2023-11-16T22:21:22+00:00 CRITICAL Uncaught Error: Class “WC_Deprecated_Action_Hooks” not found in /home/L/labhusetno/www/wp-content/plugins/woocommerce/includes/class-woocommerce.php:695 Stack trace: #0 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): WooCommerce->init() #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /home/L/labhusetno/www/wp-settings.php(643): do_action() #4 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’) #5 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’) #6 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’) #7 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’) #8 {main} thrown i /home/L/labhusetno/www/wp-content/plugins/woocommerce/includes/class-woocommerce.php p? linje 695

2023-11-16T22:27:37+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/plugins/woocommerce/includes/react-admin/core-functions.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php:75 Stack trace: #0 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Admin/Composer/Package.php(65): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->init() #1 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Admin\Composer\Package::init() #2 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Packages.php(44): Automattic\WooCommerce\Packages::load_packages() #3 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Packages::on_init() #4 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #5 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action() #6 /home/L/labhusetno/www/wp-settings.php(506): do_action() #7 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’) #8 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’) #9 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’) #10 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’) #11 {main} thrown in /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php on line 75

2023-11-16T22:29:36+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/RelatedProducts.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php:90 Stack trace: #0 /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypesController.php(66): Automattic\Jetpack\Autoloader\jpb66f0c116f87680df45402a303db6f40\PHP_Autoloader::load_class() #1 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Blocks\BlockTypesController->register_blocks() #2 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #3 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action() #4 /home/L/labhusetno/www/wp-settings.php(643): do_action() #5 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’) #6 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’) #7 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’) #8 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’) #9 {main} thrown i /home/L/labhusetno/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php p? linje 90

2023-11-16T22:29:36+00:00 CRITICAL Uncaught Error: Failed opening required ‘/home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/SettingsNavigationFeature.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/L/labhusetno/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php:90 Stack trace: #0 [internal function]: Automattic\Jetpack\Autoloader\jpb66f0c116f87680df45402a303db6f40\PHP_Autoloader::load_class() #1 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Admin/Features/Features.php(377): class_alias() #2 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Admin/Features/Features.php(60): Automattic\WooCommerce\Admin\Features\Features->register_internal_class_aliases() #3 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Admin/Features/Features.php(51): Automattic\WooCommerce\Admin\Features\Features->__construct() #4 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/Loader.php(66): Automattic\WooCommerce\Admin\Features\Features::get_instance() #5 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/Loader.php(56): Automattic\WooCommerce\Internal\Admin\Loader->__construct() #6 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(192): Automattic\WooCommerce\Internal\Admin\Loader::get_instance() #7 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(97): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->hooks() #8 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(81): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->on_plugins_loaded() #9 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Admin/Composer/Package.php(65): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->init() #10 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Admin\Composer\Package::init() #11 /home/L/labhusetno/www/wp-content/plugins/woocommerce/src/Packages.php(44): Automattic\WooCommerce\Packages::load_packages() #12 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Packages::on_init() #13 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #14 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action() #15 /home/L/labhusetno/www/wp-settings.php(506): do_action() #16 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’) #17 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’) #18 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’) #19 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’) #20 {main} thrown in /home/L/labhusetno/www/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

2023-11-16T22:36:59+00:00 CRITICAL Uncaught Error: Class “ActionScheduler_Store” not found in /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler.php:25 Stack trace: #0 /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler.php(145): ActionScheduler::store() #1 /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php(58): ActionScheduler::init() #2 /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_Versions.php(59): action_scheduler_initialize_3_dot_6_dot_4() #3 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(322): ActionScheduler_Versions::initialize_latest_version() #4 /home/L/labhusetno/www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #5 /home/L/labhusetno/www/wp-includes/plugin.php(517): WP_Hook->do_action() #6 /home/L/labhusetno/www/wp-settings.php(506): do_action() #7 /home/L/labhusetno/www/wp-config.php(96): require_once(‘/home/L/labhuse…’) #8 /home/L/labhusetno/www/wp-load.php(50): require_once(‘/home/L/labhuse…’) #9 /home/L/labhusetno/www/wp-blog-header.php(13): require_once(‘/home/L/labhuse…’) #10 /home/L/labhusetno/www/index.php(17): require(‘/home/L/labhuse…’) #11 {main} thrown in /home/L/labhusetno/www/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler.php on line 25

Hi there @paaljoachim ??

Welcome to WooCommerce Support. I’d be happy to help you with this.

The WooCommerce version I am having some trouble with is 8.2.2.
The main issue is switching between PHP 8.1 and 8.0 and how it affects multiple plugins. As there are a few plugins that were active with PHP 8.1 then deactivated and reactivated with PHP 8.0 causing errors.

From what I gather, this is tested with a development site. While switching PHP version might impact other plugins on the site, we’ll focus on what’s happening with regard to WooCommerce here.

Just to clarify, are you able to identify any issues when only the WooCommerce plugin (version 8.3.0) is activated, with either 7.4.x, 8.1.x or 8.2.x version of PHP? If yes, kindly attach further details on how to reproduce that. In the attached video, I did not seem to find such a test to have been performed.

Looking forward to hearing back from you!

Hey @anastas10s

I have made a few test sites. The following test site has almost nothing on it.
It has the Twenty Twenty Four default theme active. Uses many of the same plugins as the other dev and live site.

Earlier today I received the standard.
[Labhuset NY] Your Site is Experiencing a Technical Issue

Howdy!

WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, WooCommerce.

First, visit your website (https://labhuset.no/new/) and check for any visible issues. Next, visit the page where the error was caught (https://labhuset.no/new/new/wp-admin/plugin-install.php) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

https://labhuset.no/new/wp-login.php?action=enter_recovery_mode&rm_token=LUHwyj9ih3mfEeqmO0T3c8&rm_key=d40qECcYeLSNiODmQZ0xn0

To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:

WordPress version 6.4.1

Active theme: Twenty Twenty-Four (version 1.0)

Current plugin: WooCommerce (version 8.3.0)

PHP version 8.1.13

Error Details

=============

An error of type E_ERROR was caused in line 90 of the file /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php. Error message: Uncaught Error: Failed opening required '/home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Admin/PluginsHelper.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php:90

Stack trace:

#0 /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(154): Automattic\Jetpack\Autoloader\jpb66f0c116f87680df45402a303db6f40\PHP_Autoloader::load_class()

#1 /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(98): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->includes()

#2 /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(81): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->on_plugins_loaded()

#3 /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Admin/Composer/Package.php(65): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->init()

#4 /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Admin\Composer\Package::init()

#5 /home/L/labhusetno/www/new/wp-content/plugins/woocommerce/src/Packages.php(44): Automattic\WooCommerce\Packages::load_packages()

#6 /home/L/labhusetno/www/new/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Packages::on_init()

#7 /home/L/labhusetno/www/new/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#8 /home/L/labhusetno/www/new/wp-includes/plugin.php(517): WP_Hook->do_action()

#9 /home/L/labhusetno/www/new/wp-settings.php(506): do_action()

#10 /home/L/labhusetno/www/new/wp-config.php(100): require_once('/home/L/labhuse...')

#11 /home/L/labhusetno/www/new/wp-load.php(50): require_once('/home/L/labhuse...')

#12 /home/L/labhusetno/www/new/wp-admin/admin.php(34): require_once('/home/L/labhuse...')

#13 /home/L/labhusetno/www/new/wp-admin/plugin-install.php(16): require_once('/home/L/labhuse...')

#14 {main}

? thrown

Hi @paaljoachim

The error message you provided indicates that the WooCommerce plugin is trying to open a file that doesn’t exist or isn’t accessible. The missing file is woocommerce/src/Admin/PluginsHelper.php.

Here are a few steps you could take to resolve this issue:

1. Use an FTP client or your hosting provider’s file manager to check if the file exists in the mentioned path. If it doesn’t, that’s likely the source of the problem.
2. If the file is missing, the simplest solution would be to reinstall the WooCommerce plugin. Please ensure to backup your site before doing this to prevent any data loss.
3. If the file does exist, it’s possible that WordPress doesn’t have the necessary permissions to access it. You can change the file permissions via FTP or your hosting provider’s file manager. A typical permission setting for WordPress files is 644 and for directories is 755.

If none of the above steps work, I recommend contacting your hosting provider, as suggested in the error email. They may be able to provide more insight into the issue.

I wish I could help more, but hopefully, this gets you going in the right direction to get the job done.

There are some errors that are not fatal errors. I am bringing this up in the Make WordPress core slack channel #core-upgrade-install. I also made this Trac Ticket: https://core.trac.www.ads-software.com/ticket/60419

The main point is in having some minor errors that are not visible for admins or others not have error emails sendt out or atleast phrasing it differently. This will make it easier for plugin and theme support folks.

Hi @paaljoachim,

Thank you for your active involvement in the WordPress community. We appreciate your efforts in bringing this to the attention of the WordPress core team and creating a Trac ticket.

Your suggestion about handling non-fatal errors differently is indeed valuable. It would indeed help reduce unnecessary error notifications and make it easier for plugin and theme support teams to focus on more critical issues.

Please continue sharing your feedback and suggestions in the WordPress core slack channel and Trac. Your contribution is essential in improving the WordPress ecosystem, including WooCommerce.

Thank you once again for your initiative and dedication. If you have any more questions or need further assistance, feel free to ask.