JetPack plugin failure

  • Resolved keithwillenson

    (@keithwillenson)


    9 months, 2 weeks ago

    A few hours ago I got this email:

    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, Jetpack.

    First, visit your website (https://sitename.com/) and check for any visible issues. Next, visit the page where the error was caught (https://sitename.com/wp-admin/admin.php?page=phone-orders-for-woocommerce) 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.

    link removed

    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.5.4
    Active theme: Neve (version 3.8.7)
    Current plugin: Jetpack (version 13.5)
    PHP version 7.4.33

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 27 of the file /home/customer/www/sitename.com/public_html/wp-content/plugins/jetpack/load-jetpack.php. Error message: require_once(): Failed opening required ‘/home/customer/www/sitename.com/public_html/wp-content/plugins/jetpack/class.jetpack-network.php’ (include_path=’.:/usr/local/php74/pear’)

    Through the special “recovery mode” link. I disabled JetPack. The site came back on line.

    Using FTP, I renamed plugins/jetpack to plugins/jetpack_bad so I could reinstall JetPack. That did not work. WooCommerce still recognized that JetPack was installed.

    I created a directory called bad_plugins at the same level as plugins and moved jetpack_bad into that directory. After confirming that WooCommerce no longer recognized that I had JetPack as a plugin, I installed JetPack using the plugin installer. Everything seems to be working fine.

    Is anyone interested in looking at the malfunctioning code?

Viewing 1 replies (of 1 total)

  • Hi @keithwillenson,

    Thanks for reaching out and sharing your experience.

    The E_COMPILE_ERROR tends to show when something interrupts the upgrade process on Jetpack. Were you recently updating to the most recent Jetpack release?

    Typically, our solution for this error is to ask folks to uninstall and reinstall Jetpack—which you figured out on your own! We also suggest manually deleting the Jetpack plugin via FTP if that doesn’t solve it.

    Let us know if anything else comes up.

Viewing 1 replies (of 1 total)
  • The topic ‘JetPack plugin failure’ is closed to new replies.

Tags