Through my years as a plugin author, theme developer, and website builder, I’ve logged into a lot of other peoples’ WordPress installations. More often than not, those people have plugin or WordPress core updates they haven’t done.
Through blogs, Twitter, and other social media, I see people explain why they don’t do updates.
- “They break my site!”
- “It works fine as it is.”
- “I don’t need new features.”
- “Last time I did an update my site blew up.”
- “What if my plugins don’t work with the new WordPress version??”
WordPress updates aren’t a bad thing. You just need to be able to predict if there will be a problem.
Yep, there are ways to know beforehand if updating a plugin or WordPress core will break your site. It’s not a 100% guarantee, but it’s a pretty good way to guess.
Changelogs tell you everything you need to know about plugin and core updates.
A changelog is a list of changes that have been made. This includes a list of bug fixes, new features, and any other tweaks that were made since the previous version.
Here’s an example from my plugin Naked Social Share:
- Fixed a glitch with the Pinterest share button where it wasn’t picking up the featured image.
- Added German translation. Thanks to jackennils
- Changed cache time to 3 hours, as advertised. It was set to only 2 hours for some reason.
From this you can see that in version 1.2.2 I added some new translation files, which wouldn’t affect the performance of the plugin at all, and I changed the cache time. Both of those are very minor changes.
Then, in 1.2.3 I fixed a but where the Pinterest share button wasn’t picking up the correct image. So this change solves a problem.
But from this information, you can tell that nothing major was changed. There was no overhaul of the whole plugin, I didn’t completely redo the settings panel, etc. All the changes are pretty small tweaks, so you shouldn’t expect either update to affect the performance or operation of your site.
How to find out if a WordPress core update will break your site.
Let’s use an example situation to figure out if updating to a new version of WordPress will break your site or not.
So let’s say there’s a new WordPress version (4.3). We’re going to try to guess whether or not your plugins will break as a result of this update.
Step #1: Read the changelog for information about the new version.
In our example, we’re upgrading our site to WordPress version 4.3 (from 4.2.x). So the first step is to hop over to the upgrade page where they paste the changelog.
- Formatting Shortcuts while using visual editor.
- Use * or – to start an unordered list.
- Use 1. or 1) to start an ordered list.
- Use ## for H2 and ### for H3 (etc, through H6).
- Use > to transform text into blockquote.
- All new pages that you create will have comments turned off by default.
- Menus can now be managed with the Customizer, which allows you to see “live” preview changes without changing your site for visitors until you are ready.
- Customizer improvements including enhanced accessibility, smoother menu creation and location assignment, and the ability to handle nameless menus.
- Take control of another piece of your site with the Site Icon feature. You can now manage your site’s favicon and app icon from the Admin area.
- Customize link added in the toolbar to swiftly make changes to your site.
- Better Passwords. Password field will be automatically filled with a strong password, while adding new users and resetting the password.
This is kind of a big list, but we can break it down into a few categories:
- Visual editor (new shortcodes)
- Comments and whether or not they appear on pages
- Customizer changes—addition of menus and “site icons” (favicons)
- Passwords—changes to how they’re created and sent to new users
Step #2: Go through your list of plugins and ask yourself if they relate to any of these areas.
It’s time to do some analysing! Go through your list of plugins and ask yourself a few questions for each one:
- Does this plugin do something to the visual editor? Does it add custom buttons or change the behaviour?
- Does this plugin change the behaviour of when comments appear?
- Does this plugin make any changes to the WordPress Customizer?
- Does this plugin have anything to do with user logins or membership or accounts? If user accounts and passwords are involved, then the plugin might be affected by the new password changes.
If the plugin is unrelated, it probably won’t be affected by the new version.
If the plugin has nothing to do with any of those areas, then the new WordPress update probably won’t affect the operation of the plugin. This means you can pretty confidently perform the update.
If the plugin does relate, do some more digging.
However, if the plugin is related to one of those areas, then it could possibly be affected by the update. Here’s where you can dig a little deeper.
- Check when the plugin was last updated. Is it listed as being tested with the new version (4.3)? If it was tested with 4.3 then it’s probably works with the new update. But if the plugin hasn’t been updated for months or years, then it’s more likely there might be a conflict.
- Check the plugin’s support forums. Is anyone complaining about issues with the new WordPress update?
It’s all about making an educated guess.
Unless you read through every line of code, there’s no way to know 100% for sure whether or not your site will be affected by updates.
But if you take time to read the changelogs and relate those to your plugins, you can make a pretty good guess about whether or not there could be a conflict. Combine that with checking last updated dates, tested versions, and support forums, and you’ll be in pretty good shape!
If you want to be as careful as possible then the best thing to do is create a staging site that’s an exact duplicate of your live one and perform the updates on the staging site first to see what happens.