In my last post, I talked about the safest way to update WordPress plugins. Even if you take all those steps, an update still might have a hiccup. Don’t panic! Here are a few ways things can glitch, and how you can fix it.
It’s helpful to note the basic process WordPress goes through when updating a plugin. First, it puts the site into maintenance mode (more on that below), then it deletes all the existing files for that plugin. It then downloads an archive of the new plugin, and unpacks it into the same folder. Finally, it marks the update as completed and you’ll see that glorious, green checkmark next to the plugin.
But if that doesn’t happen, here are a few things that might be going on:
The plugin update just runs and runs and runs…
The most common issue I encounter when updating is that the process just keeps going and never actually says it’s done. This is most common on underpowered, shared servers (I’m looking at you, Bluehost and HostGator!).
If it’s been more than a couple of minutes, try opening the plugins page in a new tab (leaving the current update running). Compare the version number on the new tab with the previous version number. You may find that the update actually did complete, it just never gave you that green checkmark. If that’s the case, just close the first tab and you’re good to go.
If it’s the old version and still says an update is needed, wait another minute or two and refresh the page. If it’s still the old version, try running the update again. And if you run into something else, read on.
Your site gets stuck in “maintenance mode.”
When WordPress runs an update, it first goes into maintenance mode, and will display a simple page to your visitors that says:
Briefly unavailable for scheduled maintenance. Check back in a minute.
It does this by adding a file called .maintenance in your home folder (including the leading period).
After the update completes, the .maintenance file should be removed automatically. But if the update stalls out and that file doesn’t get removed, your site will get stuck there.
To fix it, log in to your server via FTP, locate the home folder (usually /public_html/) and simply delete the .maintenance file. (If you don’t see it, you may need to tell your FTP program to show hidden files.)
The plugin didn’t install all the new files.
If the plugin update doesn’t complete, you might also end up with an empty folder for the plugin, or a folder with just some of the files installed.
For example, if you’re updating the WordPress SEO plugin, its files reside in the /wp-content/plugins/wordpress-seo/ folder. Since the update process requires removing the files, download a new zipfile, and then unzipping it back into the folder, if it stalls out and the new files don’t all get added back to that folder, you’ll run into problems.
There’s one file in every plugin that contains information about the plugin, such as the plugin name and the author. If that file doesn’t exist, the next time you load a page in your dashboard, WordPress will realize this and deactivate the plugin (and it will show a notice at the top of your screen).
However, if that file is there, but other files are missing from the plugin, you may see other errors, such as PHP Fatal Errors. You might also get the “white screen of death” (see below).
If you simply try to reinstall the plugin, WordPress will kick out an error because the folder already exists.
To fix this, you can either log in with FTP and delete the plugin folder completely, and then reinstall the plugin. Or, you can restore the plugin’s contents from the backup you made before updating.
You get the “white screen of death.”
This is similar to the above – but it happens when there is a “fatal error” of some kind…and you end up with just a blank, white screen and nothing else.
It usually happens because of an incompatibility between your server and the new version of the plugin. In this case, the best thing to do is log in with FTP, delete the plugin’s folder, and then restore the previous version of the plugin from a backup.
It’s also possible to download a previous plugin version directly from the WordPress repository. If you’re viewing a plugin’s page, go to the “Developers” tab and you can download the zipfiles of previous versions from there.
It updated fine, but now it doesn’t work quite right.
If it’s a minor issue, try updating all your other plugins, your theme, and WordPress core to the latest version. Sometimes that will fix it, as it brings everything current.
If it’s a major issue, you may want to consider rolling back to the previous version of the plugin, and posting in the support forms as I described above. Most plugin authors are incredibly helpful and responsive, and if you’re nice — and give them as much information about the issue as possible — they’ll usually bend over backwards to help you get it sorted out.
If you don’t want to deal with any of this stuff…
…let me take care of updates for you! My “Inner Peace” WordPress support services includes, among many other services, regular updates — and if updates glitch or break anything, I’ll fix it. I usually have things fixed up before anyone (including you) knows something went wrong. Learn more about my WordPress support plans here.