{"id":1,"date":"2019-10-30T00:05:52","date_gmt":"2019-10-30T00:05:52","guid":{"rendered":"http:\/\/invouq.com\/?p=1"},"modified":"2021-05-27T18:10:04","modified_gmt":"2021-05-28T01:10:04","slug":"how-to-do-a-major-wordpress-update-without-killing-your-site","status":"publish","type":"post","link":"https:\/\/www.invouq.com\/how-to-do-a-major-wordpress-update-without-killing-your-site\/","title":{"rendered":"How To Do a Major WordPress Update Without Killing Your Site"},"content":{"rendered":"\n

It\u2019s usually an excellent idea to update WordPress. After all, it\u2019s an important part of keeping your website secure and running well.<\/p>\n\n\n\n

The danger comes with major <\/em>updates to WordPress. These updates bring significant changes in how the core of WordPress works. They can break themes and plugins and leave your website a total mess if you aren\u2019t careful.<\/strong><\/p>\n\n\n\n

What Is a Major Update?<\/h2>\n\n\n\n

A major update is something that makes fundamental changes to the way the software operates, adds new features, and adds or removes files from the underlying codebase.<\/p>\n\n\n\n

It\u2019s these major changes that can cause problems. If WordPress makes major changes to its core files and a theme or plugin author isn\u2019t keeping up, then your site could end up broken.<\/p>\n\n\n\n

Version Numbering<\/h3>\n\n\n\n

Like most software, WordPress and its plugins use numbers to keep track of the software versions as they\u2019re produced.\u00a0 At the time of writing, the current version number for WordPress is 5.4.2.<\/p>\n\n\n\n

WordPress Versioning<\/h3>\n\n\n\n

The core of WordPress does things a little differently than other software, including WordPress plugins. The first two numbers in the sequence together denote a major update, not just the first number by itself.  From the WordPress documentation:<\/p>\n\n\n\n

\u201cA major WordPress version is dictated by the first two sequences. For example, 3.5 is a major release. So is 3.6, 3.7, all the way up to 4.0. Version 4.0 is no different than 3.9 and 4.1. There isn\u2019t a \u201cWordPress 3\u201d or \u201cWordPress 4\u201d \u2013 we\u2019re weird like that for historical reasons.\u201d<\/p><\/blockquote>\n\n\n\n

And:<\/p>\n\n\n\n

\u201cA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.\u201d<\/p><\/blockquote>\n\n\n\n

How Do I know What Version I\u2019m On?<\/h2>\n\n\n\n
\"WordPress<\/a>
“At a Glance” WordPress Admin Widget.
This site is several major versions behind.<\/figcaption><\/figure><\/div>\n\n\n\n

To know if you\u2019re facing a major update, you need to know what version you\u2019re currently on.  This should be trivial, but most of the places where you\u2019d go to look at your version number only show it when you\u2019re on the latest version.  Otherwise, you\u2019ll see a prompt to upgrade instead with no clue if this is a major update or not.<\/p>\n\n\n\n

The one place that\u2019s usually reliable is in your admin area.  Look for a box titled “At a Glance” like the one above. It’ll show you what version you’re on and a button with the latest version number if an update is available.<\/p>\n\n\n\n

Wait a Minute<\/h2>\n\n\n\n

If you do have a major update available, wait before updating.  Get ready first.<\/strong><\/p>\n\n\n\n

Quite often, there\u2019ll be a bug fix release a few weeks after the major update.\u00a0 I recommend to my clients that they wait for this release to come out before upgrading. At the time of writing, the next major release of WordPress will be 5.5, so I recommend waiting until version 5.5.1 comes out before doing the update.<\/p>\n\n\n\n

Example: WordPress version 5.0 came out on Dec 6, 2018. Version 5.0.1 came out 6 days later and 5.0.2 came out 7 days after that.  Between those two subsequent versions, more than 80 bugs were fixed!<\/strong><\/em><\/p>\n\n\n\n

You can view the WordPress changelog here<\/a>.<\/p>\n\n\n\n

Make a Backup<\/h2>\n\n\n\n
\"UpdraftPlus<\/a>
UpdraftPlus<\/figcaption><\/figure><\/div>\n\n\n\n

Before doing any updates, I always recommend making a backup of WordPress files and the database.\u00a0 You must get both; the files are useless without the database and vice versa.<\/p>\n\n\n\n

I use the UpdraftPlus plugin<\/a> to do this. I set up UpdraftPlus to automatically backup my site to off-site storage. While I pay for UpdraftPlus, the free version will do this too. Offsite backups also protect me should anything ever happen to my hosting provider.\u00a0<\/p>\n\n\n\n

Pro Tip: Before doing anything else make sure you have backups in place and know how to restore from them. If you\u2019re not sure, install UpdraftPlus and make a backup before doing any updates.<\/strong><\/p>\n\n\n\n

UpdraftPlus also provides instructions on how to restore from a backup in case things go sideways on you. <\/a><\/p>\n\n\n\n

Another great option is a service like VaultPress.  This is a premium service that\u2019ll also make regular off-site backups for you.<\/p>\n\n\n\n

Your hosting provider may also be making regular backups for you.\u00a0 Double-check to make sure and make sure you know how to restore from a backup or where to get help if needed.<\/p>\n\n\n\n

You can also use FTP to download all of your files and phpMyAdmin (or equivalent) to get a copy of your database. This is a little advanced for this article, so search Google if you\u2019d like to learn more.<\/p>\n\n\n\n

Get Prepared<\/h2>\n\n\n\n

Before doing a major WordPress update, update all the plugins first.  <\/p>\n\n\n\n

This is crucial.  Good plugin developers will make changes ahead of a major release to prepare for it.  Updating the plugins first can save you from a world of hurt.<\/p>\n\n\n\n

The same is true for your themes. Make sure that they\u2019re updated as well.  Select the themes you wish to update and click on the Update Themes button.<\/p>\n\n\n\n

\"WordPress<\/a>
Select your themes then hit Update<\/figcaption><\/figure>\n\n\n\n

If you\u2019re using a premium theme from ThemeForest then you\u2019ll need to update it using one of the methods described here.<\/a><\/p>\n\n\n\n

Pro Tip: Have a look at your pages, posts, membership areas, your shopping cart, any calendars, etc.  Use a desktop and a phone to look at your site.  Take a screengrab<\/a> of your various page types. The goal here is to make sure that you have the \u201cbefore\u201d view of your site in mind.<\/strong><\/p>\n\n\n\n

Do it!<\/h2>\n\n\n\n
\"WordPress<\/a>
Once you’re ready, update WordPress<\/figcaption><\/figure><\/div>\n\n\n\n

Now it\u2019s time. Do the update by clicking on the button on the WordPress Updates screen.  Your site will go into maintenance mode for a few moments while the update takes place.<\/p>\n\n\n\n

Review the site again to make sure everything is working. If you\u2019re not sure that everything is right, refer to the screen grabs you took earlier. Make sure to try your contact forms and make a test purchase if you have a store.<\/p>\n\n\n\n

What About Automatic Updates?<\/h2>\n\n\n\n

This all seems like a lot of work, and many hosting providers will do automatic updates for you.  <\/p>\n\n\n\n

It sounds easy, shouldn\u2019t you just do that?<\/p>\n\n\n\n

\"Toy<\/a>
Thoughtless tin robot…<\/figcaption><\/figure><\/div>\n\n\n\n

The problem with automatic updates is that they\u2019re thoughtless. Updates are applied as soon as they are available, whether or not your plugins or themes are ready.  They can, and do, easily break WordPress websites.<\/p>\n\n\n\n

Automatic updates will break your site without you knowing because you\u2019re not even there to notice any problems.\u00a0 It\u2019s not uncommon for a site to be messed up for days before the owner notices, and it\u2019s oftentimes because a client told them.\u00a0 Panic time!<\/p><\/blockquote><\/figure>\n\n\n\n

Summary<\/h2>\n\n\n\n

It seemed like this was a lot of work to do the upgrade.\u00a0 It kind of was if you had to get backups in place first.\u00a0 Once you\u2019ve done this once or twice, it\u2019ll go much smoother.<\/p>\n\n\n\n

The good news is that you now have the confidence to do this the right way!\u00a0 You know how to be thoughtful about updates and what steps to take to ensure success.<\/p>\n\n\n\n

P.S. If you\u2019d rather not have to mess with any of this, I do have WordPress Maintenance Plans available.<\/a> I manually update WordPress sites in this thoughtful manner, and I automatically take care of any issues depending on the plan you choose.<\/p>\n","protected":false},"excerpt":{"rendered":"

When you update Wordpress be on the lookout for a major update. These can kill your website. Your layout can break, plugins can stop working, and you might even get the dreaded white screen of death! What is a major update, anyway, and how can we update WordPress safely?<\/p>\n","protected":false},"author":1,"featured_media":862,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35],"tags":[51],"_links":{"self":[{"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/posts\/1"}],"collection":[{"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/comments?post=1"}],"version-history":[{"count":0,"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/posts\/1\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/media\/862"}],"wp:attachment":[{"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/media?parent=1"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/categories?post=1"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.invouq.com\/wp-json\/wp\/v2\/tags?post=1"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}