Too many “e_error” errors

  • Resolved depannerobot

    (@depannerobot)


    6 months, 4 weeks ago

    Hello everyone, I am getting a lot of “E-ERROR” errors on the WooCommerce plugin, but also with other plugins.
    The website crashes, then comes back on its own and works until the next bug occurs 15 minutes, 24 hours, or 3 days later!
    Is this a problem with the plugin, the database, or the files (reading/writing)?

    eg:

    Une erreur de type E_ERROR a été causée dans la ligne 102 du fichier /htdocs/wp-content/plugins/woocommerce/src/Internal/DependencyManagement/RuntimeContainer.php. Message d’erreur : Uncaught Automattic\WooCommerce\Internal\DependencyManagement\ContainerException: Attempt to get an instance of class 'Automattic\WooCommerce\Internal\ComingSoon\ComingSoonRequestHandler', which doesn't exist. in /htdocs/wp-content/plugins/woocommerce/src/Internal/DependencyManagement/RuntimeContainer.php:102 Stack trace: #0 /htdocs/wp-content/plugins/woocommerce/src/Internal/DependencyManagement/RuntimeContainer.php(75): Automattic\WooCommerce\Internal\DependencyManagement\RuntimeContainer->get_core('Automattic\\WooC...', Array) #1 /htdocs/wp-content/plugins/woocommerce/src/Container.php(66): Automattic\WooCommerce\Internal\DependencyManagement\RuntimeContainer->get('Automattic\\WooC...') #2 /htdocs/wp-content/plugins/woocommerce/includes/class-woocommerce.php(338): Automattic\WooCommerce\Container->get('Automattic\\WooC...') #3 /htdocs/wp-content/plugins/woocommerce/includes/class-woocommerce.php(239): WooCommerce->init_hooks() #4 /htdocs/wp-content/plugins/woocommerce/includes/class-woocommerce.php(157): WooCommerce->__construct() #5 /htdocs/wp-content/plugins/woocommerce/woocommerce.php(47): WooCommerce::instance() #6 /htdocs/wp-content/plugins/woocommerce/woocommerce.php(62): WC() #7 /htdocs/wp-settings.php(545): include_once('/htdocs/wp-cont...') #8 /htdocs/wp-config.php(86): require_once('/htdocs/wp-sett...') #9 /htdocs/wp-load.php(50): require_once('/htdocs/wp-conf...') #10 /htdocs/wp-login.php(12): require('/htdocs/wp-load...') #11 {main} thrown

    Thx 🤨

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    6 months, 4 weeks ago

    Hi there,

    Thank you for sharing the detailed error message.

    The error you’re seeing indicates that WooCommerce (or one of its components) is trying to load a class that doesn’t exist. This can often happen due to:

    • Incomplete or corrupted plugin files (especially after updates).
    • Plugin conflicts with other plugins or themes.
    • Caching issues or server-side object cache problems.

    Could you please confirm if you made any changes on your site after which the issue started appearing? For example, did you update any plugin or install a new one?

    Also, Here’s what I’d suggest as next steps:

    1. Reinstall WooCommerce – Download the latest version from wordpress.org/plugins/woocommerce and reinstall it to ensure no files are missing or corrupted.
    2. Conflict Test – Temporarily switch to a default theme (like Twenty Twenty-Four) and deactivate all plugins except WooCommerce to see if the issue persists. Here is the guide to help you on how to run a conflict test https://woocommerce.com/document/how-to-test-for-conflicts/
    3. Clear Server Cache – Make sure any server-side or object cache is cleared after reinstalling.

    In the meantime, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:

    • System Status Report which you can find via WooCommerce > Status
    • Fatal error logs (if any) under WooCommerce > Status > Logs.

    Please use https://pastebin.com/ or https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further

    Thread Starter depannerobot

    (@depannerobot)

    6 months, 4 weeks ago

    @shahzeenfarooq thank you

    Tomorrow i wil reinstall woo, do a conflict test. Server cache is done

    System Status Report : https://pastebin.com/s0PysWau

    Fatal error logs is too big >512 k, so it’s on my own server : http://depannerobot.fr/partage/fatal-errors-2025-09-25.log

    Thx

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    6 months, 4 weeks ago

    Hi there!

    Sure, take your time and let us know what you find during the conflict test. Also, thank you for sharing the system status report and the error log.

    First, I would suggest updating WooCommerce to the latest version. From the log you shared, the issue seems to be related to the Jetpack plugin.

    Please try deactivating the Jetpack plugin first and see if that resolves the issue. If not, then proceed with running a complete conflict test.

    Thread Starter depannerobot

    (@depannerobot)

    6 months, 3 weeks ago

    Hello, I have disabled JetPack and, for now, I haven’t had any further errors. Fingers crossed.

    Moses M. (woo-hc)

    (@mosesmedh)

    6 months, 3 weeks ago

    Hi @depannerobot,

    That’s great news — thank you for the update! I’m glad you were able to identify the issue and that disabling Jetpack resolved it for now.

    For the error itself, I’d recommend creating a topic here so the Jetpack team can review it directly and provide a proper fix: https://wordpress.org/support/plugin/jetpack/

    Plugin Support thelmachido a11n

    (@thelmachido)

    6 months, 2 weeks ago

    It’s been a while since we heard back from you @depannerobot for this reason we are closing this thread. 

    If WooCommerce has been useful for your store and you appreciate the support you’ve received, we’d truly appreciate it if you could leave us a quick reviewhere: 

     https://wordpress.org/support/plugin/woocommerce/reviews/#new-post 

    Feel free to open a new forum topic if you run into any other problem. 

    Thread Starter depannerobot

    (@depannerobot)

    6 months, 2 weeks ago

    Hi

    Twodays ago I got a PayPal payments error when Jetpack was disabled.

    I just reactivated Jetpack, while leaving PayPal payment disabled.

    I’m waiting for an error to occur before sending the logs.

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    6 months, 2 weeks ago

    Hi @depannerobot,

    I understand you are monitoring after reactivating Jetpack and pausing PayPal payments, and you want to be ready to capture the right details when the error shows up. You are on the right track, and we can set things up now so the next occurrence gives us clear clues.

    Please prepare these, then share the outputs when the issue reappears

    1. Enable WooCommerce and gateway logs. In WooCommerce, go to Settings, Payments, PayPal, enable logging. After the error, check WooCommerce, Status, Logs, pick the latest PayPal log and any fatal error logs, then paste the contents to https://pastebin.com or https://gist.github.com and share the links.
    2. Turn on WordPress debug logging so PHP fatals are captured. Guide here, https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
    3. Check Jetpack connection and status. Use the Jetpack debug tool and the connection test at https://jptools.wordpress.com/debug/, then share the results.
    4. If it is intermittent, try reproducing in a safe mode. Install Health Check and Troubleshooting, enable Troubleshooting Mode, activate only WooCommerce, Jetpack, and your payment plugin, then try again. https://wordpress.org/plugins/health-check/
    5. If you need to rule out a general conflict again, here is the conflict test guide, https://woocommerce.com/document/how-to-test-for-conflicts/

    Once you have the next occurrence, please send the pastebin or gist links for the WooCommerce logs and the wp debug log, plus the Jetpack debug result links, and we will help pinpoint the cause.

    Feel free to let us know how it goes.

    Plugin Support Chris Moreira – a11n

    (@chrism245)

    6 months ago

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Too many “e_error” errors’ is closed to new replies.