• Hello! I have not updated my website in years and it’s time to get back in there and make temp changes before I build a new site. I have been getting the following error. But I’m not receiving an email. I’ve checked my bluehost info and I am an admin for the site but no email is coming.

    There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

    On Bluehost when I check PHP Errors, I see this from the past month or so:

    PHP Fatal error: Declaration of Jetpack_IXR_Client::query() must be compatible with IXR_Client::query(…$args) in /home2/dropthea/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class.jetpack-ixr-client.php on line 51

    And this from June/July:

    PHP Fatal error: __autoload() is no longer supported, use spl_autoload_register() instead in /home2/dropthea/public_html/wp-includes/compat.php on line 502

    I’m looking for help so I can go in and make a few edits, delete a page or two and simplify. I’m not a coder or website builder. I had formerly had someone who built and was admin for my site, but at the moment I’m DIY with very limited knowledge and experience. Any help would be wonderful.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator threadi

    (@threadi)

    If an error is currently occurring, the latest entries in the error log would be interesting. The two you mentioned relate to the Jetpack plugin. If they haven’t occurred again since then, they are not the cause of the current error.

    If you need help reading the error logs from your host, it’s best to contact their support team. In our experience, Bluehost is quite professional in this regard.

    If the cause of the error is a plugin, please report the error to the support forum for the plugin in question. For Jetpack, this can be found here: https://ww.wp.xz.cn/support/plugin/jetpack/

    Hey Joe, you’re running into two separate, but related issues: WordPress and Jetpack are out of sync with the PHP version your account is using, and Recovery Mode emails are going to the site’s stored admin address, which may be old or blocked, so you’re not seeing them.

    Here’s the quickest path to get back in and make edits. First, lower PHP temporarily so the site can load. In your Bluehost account manager open Advanced and use MultiPHP Manager to set the domain to PHP 7.4. This isn’t a long-term fix, just a safe bridge so the dashboard opens with older code. When you can log in again, update WordPress core to the latest, then update plugins and themes, then move PHP back up to 8.1 or 8.2. The error about __autoload points to older code on PHP 8, and the Jetpack_IXR_Client message points to an older Jetpack version on a newer PHP, so updates will resolve both once you’re back in.

    If the dashboard still won’t load after changing PHP, disable Jetpack from the file side to break the error loop. In cPanel or the Bluehost File Manager go to wp-content/plugins and rename the jetpack folder to something like jetpack.off. If that doesn’t do it, temporarily rename the entire plugins folder to plugins.off, then reload the site to confirm it comes back. Once you’re in wp-admin, rename folders back and re-activate plugins one by one after they’re updated.

    About the missing Recovery Mode email, WordPress sends that to the admin_email saved in the database, not necessarily the address you expect. If an old developer’s email is still in there, you won’t receive anything. After you can access wp-admin, go to Settings → General and confirm the Administration Email Address. If you can’t log in yet but need to change it, you can adjust the admin_email value in the wp_options table via phpMyAdmin. Also check your domain’s email routing or any external mail provider settings to be sure the mailbox exists and isn’t full; if delivery is flaky, add SMTP later with a plugin once the site is stable.

    If you just need to reset a password to get moving, try wp-login.php?action=lostpassword with a mailbox you can access. If that still doesn’t arrive, it’s another sign the stored admin email is out of date or mail isn’t configured; the PHP switch and plugin rename steps above are the faster unlocks.

    Once you’re back in and updated, bring PHP back to 8.1/8.2, re-enable Jetpack, and clear any persistent cron errors. If the Jetpack fatal error returns only when Jetpack is active, leave it off, update it to the latest, and reconnect it. If you see fresh fatal entries after all updates, copy the newest lines from the error log and we’ll help you pinpoint the exact call that’s failing.

    If you’d like us to take a closer look at the account-side logs and PHP settings, we’re happy to help. Just reach out to our support team by phone or chat and they would be happy to assist!

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

The topic ‘Critical Error Not Getting Email’ is closed to new replies.