WordPress update: how to do it without breaking your site

  • Home
  • WordPress update: how to do it without breaking your site
WordPress update: how to do it without breaking your site

A safe WordPress update always follows the same order: a fresh backup, a test on staging, then core, plugins and theme, and finally a check of the paths your company makes money on.

Have you been avoiding the “Update” button for months? Then every extra week adds more changes that will have to be installed all at once later. And the bigger the pile of new stuff, the harder it is to work out which change caused the conflict. Below is a procedure that will take the stress out of this step.

Why is putting off updates a bigger risk than the update itself?

Because the backlog piles up. Changes and unpatched vulnerabilities grow with every week, so a late jump across several versions hurts more than regular, small steps. The makers of the system recommend staying on the latest release, and for a jump across several versions they point to the extended procedure in the official WordPress update documentation. Oh, and one more thing. An update overwrites the core files, so any fix typed directly into them will simply disappear. Keep your own modifications in a child theme or in a separate plugin. And yes, regular patching is just one piece of a bigger puzzle, which is hardening your WordPress security.

Backup before the update: where to start

Without a full copy of the files and the database, we do not click “Update”. Period. The backup has to cover both, sit outside the server the site runs on, and actually be restorable (a copy nobody has ever restored is more of a hope than a safeguard). So practice a restore once, calmly, before you have to do it under pressure. What counts is a copy from the day of the update, not from a week ago. After all, orders, messages and new posts have come in since then. Don’t have a set method yet? A good starting point is a backup made with UpdraftPlus that sends the archive to external cloud storage.

Staging test environment: check the changes before your customers see them

Staging is a copy of the site where you test the update without touching production, that is, the version your visitors see. When is it essential? When you run a store, have forms connected to a CRM or a mailing system, rely on a dozen or more plugins or use a custom-built theme. Many hosting companies provide such a copy with one click in the panel. You can also set up an installation locally, on your own computer. We describe how to organize the whole deployment process in our article on staging and versioning changes.

WordPress update step by step: core, plugins, theme

One thing at a time. A single element per step, and a quick look at the site after each one. That is the only way to know what caused an error, if one appears.

  1. Core: Dashboard > Updates > “Update Now”.
  2. Plugins: one by one, starting with the critical ones, e.g. WooCommerce.
  3. Theme: the parent theme first, then the child theme.
  4. Translations: last, once everything else works.

Before you start on the plugins, look through their changelog, that is, the list of changes. Especially when the first digit of the version number changes, because that usually means something bigger is going on. And what if WordPress suddenly asks for FTP credentials? It is about who owns the files on the server. Just enter the details of the FTP account that was used to upload the site.

What to check after the update: testing the key paths

After the update, you click through the paths your company makes money on or collects leads through. Opening the home page alone proves nothing. Nothing.

  • the contact form, including whether the message actually reaches the inbox,
  • the cart and a test payment,
  • customer login and the account panel,
  • the menu and the mobile version,
  • the on-site search.

Also look at the server error log and the browser console, because a good share of faults simply cannot be seen on the screen. Only when the test on staging passes cleanly do you repeat the same sequence on production.

What to do when an update breaks the site?

First of all, don’t panic. When a critical error occurs, WordPress sends the administrator an email with a link to recovery mode, where you can turn off the plugin or theme at fault. A white screen and no access to the panel at all? Then you connect via FTP or your hosting file manager and rename the folder of the suspect plugin. That deactivates it.

The message about a failed update will disappear once you delete the .maintenance file from the main installation folder. Leave restoring the backup for the very end, as a last resort. But be careful: if after the failure you see strange redirects or files that nobody uploaded, the site may have been infected. In that case, removing viruses from the site will help.

Automatic WordPress updates: which to turn on and which to keep manual

WordPress installs minor fixes and core security patches by itself, in the background. Major releases still require a click, which the update guide on WordPress.org confirms. You turn on automatic updates for plugins and themes one by one, on the list in the panel. With simple add-ons, that is convenient. With a store and integrations? In my opinion, it is better to keep a close eye on things. The rule is actually simple: automation where a failure costs nothing, manual and tested where sales are at stake. And a steady rhythm, e.g. once a month, works much better than bursts of activity every six months.

A WordPress update stops being a risk when it has a fixed procedure: backup, staging, elements one by one and a test of the sales paths. After a few such cycles it is fifteen minutes of work, not a whole nervous evening. Want to handle it yourself and know exactly what you are clicking? WordPress and WooCommerce training will come in handy.

Frequently asked questions

How often should I update plugins and WordPress?

Regularly, in a fixed cycle, e.g. every month. Install security fixes right away, because they close known vulnerabilities. Install major releases only after a test on a copy of the site.

Can I update WordPress without staging?

With a small brochure site and a fresh backup, usually yes. In an online store or on a site with integrations, better not, because an error hits orders and leads right away.

What should I do when the site shows a critical error after an update?

Check the administrator inbox, open the recovery mode link from the email and turn off the plugin or theme that caused the error. Without access to the panel, rename the plugin folder via FTP. Didn’t help? Restore the backup.

Book a free consultation

Provide your phone number or schedule a meeting