Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @depannerobot

    Thanks for sharing the error logs.

    To isolate the issue, we’ll need you to do a conflict test. Please temporarily disable all plugins other than WooCommerce and then reinstall Jetpack. With only WooCommerce and Jetpack, do you see the issue?

    You can also do this test on a staging environment if that is more convenient.

    Let us know what you find out.

    Thread Starter depannerobot

    (@depannerobot)

    @lastsplash i can’t disable all plugins because i need them for my shop.

    maybe i need to copy all website to another ? Can i ?

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @depannerobot

    Yes, you can clone your website into another and do the testing there. Many hosts call that a “staging environment”. As you mention, it can be less disruptive to do it there.

    Let us know what you find out.

    Thread Starter depannerobot

    (@depannerobot)

    hi, I disabled JetPack and no further errors

    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    Hello @depannerobot,

    Thanks for sharing that disabling Jetpack stopped the errors.

    If you’re still using WooCommerce, just a heads-up that some Woo services require an active Jetpack connection to work properly, including:

    • Automated tax calculations
    • Shipping label purchasing
    • WooCommerce Mobile App support
    • Email notifications and activity logs

    If you’d like to keep using those features — and help us investigate where these errors are coming from — we recommend:

    • Re-enabling and updating Jetpack to version 15.1 (it was at 15.0)
    • Updating WooCommerce to the latest stable release
    • Checking your logs again and sharing any new entries with us

    Looking at the logs you shared earlier, the most recent fatal errors were from September 25. A more up-to-date log after updating the relevant plugins could give us better insights into what’s going on.

    Best,

    Thread Starter depannerobot

    (@depannerobot)

    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 Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @depannerobot,

    We see our Woo colleagues have replied to your same message on this thread: https://ww.wp.xz.cn/support/topic/too-many-e_error-errors/#post-18675123

    I am going to close this thread for now, to ensure all the info are shared in the same place, so we won’t lose any useful data.

    If Jetpack support and assistance is needed at any capacity, we’ll be happy to chime in. Thanks!

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

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