Updating a plugin takes one click. Fixing a site after a bad update can take a whole afternoon. The difference is almost never luck: it is a short routine you follow every time, whether you run one site or forty.
This guide walks through that routine for premium plugins and themes, the ones you paid for or downloaded as original files, which usually update outside the normal WordPress.org flow.
Why Updates Break Sites
Most broken updates come from one of three places:
- Version clashes. A page builder add-on expects a newer version of the builder than the one you have, or the other way round.
- PHP requirements. A new release drops support for an older PHP version that your host still runs.
- Cached files. The update is fine, but your cache or CDN keeps serving the old scripts and styles, so the page looks broken.
Knowing which one you are dealing with tells you how to fix it, so it is worth reading the changelog before you click anything.
Before You Update: A Five-Minute Checklist
- Take a backup of files and database, or a snapshot if your host or updater offers one.
- Read the changelog for words like “requires”, “breaking” or “minimum PHP”.
- Check the plugin’s requirements against your WordPress and PHP versions.
- Note the current version number so you know exactly what to roll back to.
- Pick a quiet moment. Not five minutes before a sale or a client demo.
Tip: keep the previous version’s zip for anything business-critical, such as your page builder, store and forms plugins. If the new version misbehaves, you can be back in under a minute.
Update One Plugin at a Time
The “update all” button is tempting, but if something breaks after updating twelve plugins at once you have twelve suspects. Update the important ones one by one, starting with the parent plugin (for example the page builder) before its add-ons.
After each update, open the front of the site in a private window. That skips your logged-in cache and shows what visitors actually see.
Test the Pages That Make You Money
You do not need to check every page. Check the ones that matter:
- The homepage and your most visited landing page
- Product, cart and checkout pages if you run a store
- Contact and lead forms, by sending yourself a test entry
- Any page built with the plugin you just updated
If everything works, clear your cache and CDN once more so every visitor gets the new files.
How to Roll Back When Something Breaks
If a page breaks, do not start editing settings. Go back to the last version that worked first, then investigate calmly.
- Deactivate the plugin you just updated.
- Upload the previous version’s zip under Plugins, Add New, Upload Plugin and choose to replace the current version.
- Activate it again and confirm the page is back to normal.
- Check the developer’s changelog or support forum for a fix, then try the new version again on a staging copy.
Your settings live in the database, so rolling back the plugin files keeps them in place in almost every case. That is also why every BoostWP product page keeps the older versions available.
Let Updates Run Themselves
Once the routine is clear, the repetitive part is a good job for software. Boost Updater brings new versions of your premium plugins and themes into the WordPress dashboard and installs them for you, with a snapshot first so a rollback is one click away.
You still decide which sites update automatically and which ones you update by hand, and the checklist above stays useful for the big releases.
Quick Answers
Will updating a plugin delete my settings?
No. Settings and content are stored in the database, not in the plugin files. Take a backup before big releases anyway.
Should I update premium themes the same way?
Yes, with one extra rule: keep your own code in a child theme so a theme update never overwrites it.
How often should I update?
Security releases as soon as possible, everything else once a week in one calm session.