Contents3 sections
Every WordPress site has a button that says “Update now.” Most of the time, clicking it is the safest thing you can do all day. Updates fix security holes, and old software is how sites get hacked.
But every so often — rarely, and always on the one day you cannot afford it — an update and something already on your site disagree. The screen goes white. Your shop stops taking orders. Your homepage is just an error message wearing a trench coat.
A backup is the copy of your site you made before that happened. With one, the disaster is a ten-minute restore. Without one, it is a very long weekend. Here is the habit, in five small steps.
The habit, step by step
- Find your backup tool. Many web hosts (the company your site lives on) include backups in your hosting panel — look for the word “Backups.” If yours does not, install a backup plugin from your dashboard under Plugins, then Add New. Free versions are fine for most small sites.
- Run a full backup. “Full” means files and database — the database is the part that holds your posts, pages and settings. A files-only copy is half a lifeboat.
- Store it somewhere that is not your site. Download it to your computer, or send it to cloud storage. A backup that lives on the same site cannot help you when the site itself is the problem.
- Now update, one thing at a time. Update a single plugin, look at your site, then do the next. If something breaks, you know exactly which update did it — and you have the backup from ten minutes ago.
- Check the pages that earn their keep. Open your homepage, one product or post, and your contact or checkout page. If they load and work, you are done.
A worked example
Say your site runs twelve plugins and a theme, and ten of them want updates on a Tuesday morning. The habit looks like this: backup at 9:00 (five minutes, mostly waiting), twelve small updates one by one (fifteen minutes, with a look at the site after each), final check at 9:25. Total cost: about half an hour and one cup of coffee going slightly cold.
The same Tuesday without a backup looks identical — right up until update number nine, when the layout breaks and there is no copy of the working site to go back to. Same morning, very different week.
The step everyone skips
Restoring. Once, on purpose, while nothing is wrong. Take an old backup and practise putting it back, following your host’s or plugin’s restore steps. A backup you have never test-restored is a promise, not a plan — and promises are hard to cash in during a panic. We keep our own house rule on this across everything we build and teach: back up before the work, and prove the backup works before you need it.
That is the whole tip. Five quiet minutes before the exciting button, and the exciting button stays boring — which is exactly what you want from it.
New to running a site? Our five checks before buying a template walk through what to look at before you spend anything, and our Meridian build log shows how we put a site together, step by step.
The links between our posts — this one included — are made with TapToLink, our own plugin, which went live on WordPress.org today.
Working on a brand-new site instead? Start with a clean bench — here is how to clean up a fresh WordPress install.
4 comments