I did H for Heartbleed a few days ago, and now I’m doing J for Jetpack.
If you haven’t already had the email, Jetpack is vulnerable, until upgraded. The problem is, with so many people updating, if your WordPress self-hosted server times out for any reason, or something else goes wrong, you might be stuck without a website.
NEVER FEAR. If the following instructions don’t make sense to you, get in touch and I’ll do it for you.
Fixing it when a plugin causes ‘exception code’ to show on any page
It looks a bit like this – and stops you from logging into your website too: (this isn’t the exact error I’ve been seeing, but it’s a good facsimile)
What to do
- Log into your FTP or c-panel. This information will be contained in information from your host. If you don’t have this, you need to contact your host.
- If going via FTP, navigate to your wp-content/plugins folder. If you’re not sure where this is, look for your public_html folder, or a folder that looks like it might be a shortened version of the domain name you’re using.
- If you’re going in via C-panel or another browser, look too through the wp-content/plugins file..
- Select the Jetpack folder.
- Delete or rename it.
Log in. You’ll have to reinstall Jetpack. Do your updates then. Remember too, some of these updates, in rare circumstances break themes or interfere with other plugins. You can troubleshoot this by following the same instructions as above, just renaming the plugin folder. If that doesn’t help, it could be your theme. In which case, navigate to your theme folder and rename the theme, though if you do this, you’ll possibly have to reset the theme options and definitively update your widgets. It’s still better to update and untangle what happens than leave it where it could be hacked.
If this is too difficult/too complicated/not something you want to do, I’m currently offering people a $10 fix and repair on Jetpack issues. Just get in touch. Anything more, you can get in touch and I’ll do it as cheap as I can.