• Resolved PeppermintMochaPatty

    (@peppermintmochapatty)


    Received this error while in the process of adding a “project” to my site. This was one of 4 I had added within the previous hour of the receiving the fatal error.

    I only had 5 Plugins “active” at the time. They are: Akismet, Jetpack, Slider Revolution, Slider Revolution Slicey Add-on and Yoast SEO. All were up to date.

    Since WP automatically generates an email regarding the error, I am including that here:

    Howdy!

    Since WordPress 5.2 there is 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 by WordPress.com.

    First, visit your website (https://www.patriciaknightphotography.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.patriciaknightphotography.com/wp-admin/admin-ajax.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://www.patriciaknightphotography.com/wp-login.php?action=enter_recovery_mode&rm_token=jD2m0wG8nbVKYd7rSJmJju&rm_key=7bEpjCgilBPxNcvdDv73Ji

    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 5.5
    Current theme: Divi (version 4.5.8)
    Current plugin: Jetpack by WordPress.com (version 8.8.2)
    PHP version 7.3.21

    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 41 of the file /home2/pkphotog/public_html/wp-content/plugins/jetpack/load-jetpack.php. Error message: require_once(): Failed opening required ‘/home2/pkphotog/public_html/wp-content/plugins/jetpack/class.jetpack.php’ (include_path=’.:/opt/cpanel/ea-php73/root/usr/share/pear’)

Viewing 15 replies - 1 through 15 (of 38 total)
  • Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    After doing some more investigating, it appears that the class.jetpack.php file is missing when installing the plugin. I have deleted the entire Jetpack folder from the plugins folder in wp-content and did a fresh install, yet this issue persists with this fresh install.

    Received the same error a few hours ago! I also noticed the date on the Jetpack folder was today’s date although the Plugin was last updated 5 days ago.

    Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    @clove001 when did you push the Jetpack update?

    I reverted to an older version of Jetpack by uploading a previous copy of the folder. Incidentally, all files were uploaded except class.jetpack.php so I manually uploaded. After a while my site failed again and that file appears to have subsequently been deleted from the folder.

    What is going on with Jetpack?

    Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    @clove001 thanks for the info. Something weird is going on for sure. If you don’t mind me asking, who is your host?

    @peppermintmochapatty Bluehost and I can confirm now the file is being deleted from the server intermittently. Site fails on deletion and returns when I re-upload the file. Which hosting company are you using?

    Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    Additional info: So, tried to update Jetpack from a different source this time, got the same error. Searched for class.jetpack.php globally through my cPanel and noticed there is a /quarantine.class.jetpack.php.[randomnumbers] file. Went to an old site, updated WordPress to 5.5, then updated Jetpack plugin through dashboard. Got critical error when I tried to update. Went to cPanel and did global search and found that there is now two /quarantine.class.jetpack.php files, though the second one had a different set of seemingly random numbers, though the first 4 were the same. Then later I did a global search again and the files were apparently deleted. I also use BlueHost.

    Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    @peppermintmochapatty Contacted support and they have been receiving reports of issues with Jetpack. There seems to be an issue in the plugin’s script. I see from the board here others are experiencing problems as well so it looks like an issue Jetpack needs to address…hopefully this is soon!

    Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    @clove001 I contacted support earlier myself. Timewaster, at least the two tech peeps I was chatting with. I was beginning to wonder if Bluehost had been hacked.

    Thread Starter PeppermintMochaPatty

    (@peppermintmochapatty)

    On my old site, I deactivated all plugins then fresh installed jetpack, five minutes later the site had crashed and noticed that the class.jetpack.php file was just moved into .quarantine folder in the main directory. When I opened that file it looked correctly according to what it should be. My hypothetical suspicion is that BlueHost may have an anti malware or virus software that is false positive flagging the class.jetpack.php file and putting it into quarantine and then deleting the file from the jetpack plugin folder.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Hi everyone! I’m sorry to hear you’ve run into issues.

    I believe there may be two different issues outlined in this thread.

    The first one is a failed plugin update. This can happen sometimes. When it does happen, re-installing the plugin from scratch helps.

    Searched for class.jetpack.php globally through my cPanel and noticed there is a /quarantine.class.jetpack.php.[randomnumbers] file. Went to an old site, updated WordPress to 5.5, then updated Jetpack plugin through dashboard. Got critical error when I tried to update. Went to cPanel and did global search and found that there is now two /quarantine.class.jetpack.php files, though the second one had a different set of seemingly random numbers, though the first 4 were the same

    @peppermintmochapatty That quarantine.class.jetpack.php.[randomnumbers] seems to point towards a different problem. Something (a service or a plugin on your site, or maybe a security system set up by your hosting provider) is renaming the file after each installation or update of the Jetpack plugin, and that’s causing your WordPress installation to break.

    Do you happen to use a security / file scanning / anti-virus plugin or service on your site? Can you think of anything on your site that may do something like this?

    If your site is hosted with BlueHost, it may be worth checking your Bluehost dashboard as well for such services. I believe Bluehost does offer something named SiteLock for site security; do you use the service on your site? Could it be what’s renaming the plugin file? What happens when you disable it?

    @everyone I would recommend that you log in to your site via FTP or CPanel, and search for a quarantine.class.jetpack.php.[randomnumbers] file in the Jetpack plugin folder under wp-content/plugins/jetpack.

    1. If you find such a file, your site is suffering from the same problem as @peppermintmochapatty. If that’s the case, could you reply to this thread with the different security plugins and services you use on your site, as well as your hosting provider? This may help us find a common thread between y’all, and potentially a solution.
    2. If you do not find such file, try to remove the old Jetpack plugin folder and then reinstall the plugin from scratch. That should solve your issue.

    On my end, I’ve reached out to Bluehost as well to get more information about this. I’ll update this thread as well once I have more information.

    Thank you all!

    • This reply was modified 4 years, 3 months ago by Jeremy Herve.

    @jeherve I’m not finding any quarantine files and do not use Sitelock or similar. I currently have the plugin disabled because of the problem but will try reinstalling. I had uploaded a backup folder of the plugin rather than re-installing previously…would this make a difference?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @clove001 If you do not have such file, I would recommend deleting the existing Jetpack plugin folder and reinstalling from scratch. This will avoid starting from a backup that may already have the same missing file.

    Reinstalling the plugin as per your instruction 2. above and in other thread did not help.

    @afasbender Could you copy the exact error you see after reinstalling, and paste it here?

Viewing 15 replies - 1 through 15 (of 38 total)
  • The topic ‘E_COMPILE_ERROR was caused in line 41’ is closed to new replies.