Nine Things You Should Do Before Updating Your WordPress Core, Plugins, or Theme

Updated on Oct 21, 2022

WordPress makes it very easy to update your website to the latest versions of the WordPress core, plugins, and theme. Just click a few buttons, right?

Well, anyone who’s worked with WordPress for a while knows that simply pressing “update” without some serious preparation can be a recipie for disaster.

Here is a list of things you should do BEFORE updating your WordPress site!

1. Make a Backup

If you do nothing else on this list, please do this one thing: make a backup of your site. I like to use the Duplicator plugin to do this. Some web hosts like WP Engine have one-click backups in their admin panels (in addition to daily automatic backups).

Disclosure: Some of the links on this page are affiliate links. This means if you click on the link and purchase the item, I will receive an affiliate commission at no extra cost to you. I test or research each service before endorsing it. I own this site and the opinions expressed here are mine.

2. Test the Live Site Before Updating

It might seem strange to test something that is supposed to be working before you even touch it, but I’ve had cases where a site wasn’t working properly after an update, and it turned out to be a pre-existing problem that had nothing to do with the update.

Make sure the live production site is working properly BEFORE you do anything to it, or else the update could lead you on a wild goose chase while you try to figure out why your update “broke” the site (when it had nothing to do with it). Not to mention, this way you won’t be wrongly blamed for a site that was broken before you did your updates!

3. Take Screenshots of Important Pages Before Updating

I’ve had situations where I’ve updated a site, then wondered, “hmmm… was the space between the header and the body really that big before the update??” (In this particular case, nothing changed after the update; I was just paranoid).

Taking a screenshot of the Home page and any other key pages can calm your fears if you start to get paranoid and think something changed after the update. Or, it can confirm that the update did indeed break something.

A variation of this is to load some of the pages of the website in a separate browser window, leave them there, then open a new window to do the updates. Then, you can compare the new site to the old (just don’t accidentally refresh the windows with the pre-updated site!)

4. Keep a Log of Changes

When I update a site, I keep a log of every change I make. I note the old and new versions of everything I update. To make that easier, I copy the plugins section of the WordPress Updates page and paste it into Evernote. That gives me the old and new versions of every plugin that needs to be updated.

If something goes wrong, I have a list of plugins that could have caused the problem!

5. Check for Major Version Updates

Before updating, I scan the plugin version numbers to see if any are jumping to a new major version, like going from V2.9.2 to V3.0.5. If any are, I read the plugin notes to check for any compatibility problems with the new version. Same goes for themes, and the WP core.

6. Check for Recent Updates

Building on the previous point, if there has been a major update to a plugin or theme, I check to see when that update happened. If it was very recently, like yesterday, I will sometimes hold off on the update for a while and let other people be the guinea pigs to test the new version, rather than having it break my site.

7. Check Your Server’s Version of PHP

If you’re updating a site that hasn’t been updated in a very long time, there’s a good chance that it’s running an old version of PHP. Doing updates to such a site could be disastrous, because the new versions of the theme and plugins might not be compatible with your server’s version of PHP.

I like to use the Duplicator plugin to check the version of PHP. Go to Duplicator -> Tools -> PHP Information to see what version of PHP your server is running. Call a web developer if it is below 7.0.

8. Test Updates On a Staging Copy

Now that you’ve done a lot of the preliminary work, it’s time to test the updates on a staging site, i.e., a non-public copy of your site.

This can be a site hosted locally on your computer using a program like MAMP (kind of advanced), or a copy of your site online that your web developer can create for you. (Just make sure the staging site is running on the same version of PHP that your production site is).

WP Engine provides a free one-click staging copy for this purpose. Siteground offers staging copies, but you have to set up the subdomains in your DNS records first. Whatever way you do it, if you want to avoid downtime after a botched update, test on staging first!

9. Have FTP and Database Access

Sometimes, even when you do everything “right”, things go wrong. That’s why I make sure that I have FTP access to the website’s server and phpMyAdmin access to the database (or SSH access) BEFORE I update anything. That way, I know I have a way to restore the site if anything should go horribly wrong.

If you’re not a developer, then you should have a developer “on call” in case something goes south.

After the Update – Do Not Skip This!

OK, so you’ve done everything on this list, and clicked “update”, so now you’re done, right? Not quite. You need to test the production site thoroughly for any issues. Remember to clear all caches!

The one thing folks always forget to test is the contact form! Do a test submission and make sure the person at the other end receives the email. Do not skip this step!

Oh, and don’t forget to make another backup of your site, so you have a nice clean updated copy!

A Final Note

The steps I’ve outlined above should be considered the minimum you should do before updating a WordPress website. If you’re running an e-commerce site that brings in thousands of dollars per day for example, I would go over and above the steps I’ve outlined here.

Please leave questions and comments below! – Brian

Subscribe to My Posts

Join 287 other subscribers

Leave a Comment or Question

Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

4 Comments
Inline Feedbacks
View all comments
Kurt
5 months ago

Great tips Brian. Another good reason for taking screenshots of important pages before updating is that you’ll have something to send to the plugin or theme development team if there is a problem.

akhil kumar
2 years ago

This content is really informative. I really loved It.

Articles

20 Critical Problems Your WordPress Website Probably Has Right Now

20 Critical Problems Your WordPress Website Probably Has Right Now

These are the most common and dire problems that I find on existing client websites that I work on for the first time. Check your website for these issues today, or contact a web developer to do a site audit! 1. Your site is not getting backed up regularly Many...

What You Need to Know About Privacy Laws and Your Website

What You Need to Know About Privacy Laws and Your Website

There has been an avalanche of legislation in the United States and Europe regarding online privacy since the rise of the Internet. Today, publishing anything on the web requires familiarity and compliance with privacy laws to avoid the possibility of legal action or...

What You Need to Know About Using Contact Forms on your Website

What You Need to Know About Using Contact Forms on your Website

A contact form is a common feature of many business websites. After all, you want to make it as easy as possible for your visitors to get in touch with you to purchase your goods or services. However, contact forms have several important pitfalls that you may not know...

What You Need to Know About Using Fonts on Your Website

What You Need to Know About Using Fonts on Your Website

Often designers will hand me a website design that uses custom fonts (i.e., not the free ones available online). And just as often, they and the client are unaware of the costs and implications of using these fonts on the web. Web Font Licensing Costs Unfortunately,...

How to Set Up Your Domain Name, Custom Email, and Web Hosting

How to Set Up Your Domain Name, Custom Email, and Web Hosting

Sometimes I get a client who is starting from scratch and needs to get a domain name, branded email accounts, and web hosting (or sometimes they have the domain name already). Here's my process to get that all set up, along with some tips and tricks. Note, the order...

Why I Use the WordPress Divi Theme

Why I Use the WordPress Divi Theme

If you ask a WordPress developer what their favorite builder theme is, you'll get a very opinionated answer, kind of like asking a photographer what brand of camera is best, or a gamer what console is best. The truth is, there are a lot of great themes out there. Many...

My Website Accessibility Checklist

My Website Accessibility Checklist

Per United States and European law, your website needs to be designed so that folks with various types of physical or cognitive disabilities will be able to access the information or perform the functions offered on your website. Not complying could result in...

Why You Should Own Your Own Domain Name and Web Hosting Accounts

Why You Should Own Your Own Domain Name and Web Hosting Accounts

I always tell my clients to set up their own domain name and web hosting accounts and pay for with their own credit card. I do not provide hosting. Here's why I think you should not let your web developer, agency, or any third party own your web and domain name...

My Website Project Kickoff Questionnaire

My Website Project Kickoff Questionnaire

These are some questions I think about before starting a new website project. It's a great checklist to go through before starting to help you scope out your project. 1. Audience and Purpose Who is the target audience of the website? What is the site tagline, in...

Shares