PLUGIN UPDATESA safe WordPress routinePlugin updates fix security holes, and WordPress's own documentation says to always keep plugins and themes on the latest version to keep a site secure. Updates can also break a contact form, a layout or a checkout, so many teams put them off. Skipping them is the bigger risk. What works is a dull routine: small plugins update themselves, risky ones are tested first, and every update has a way back.
Which plugins can update on their own?
Small, single-purpose plugins can usually update automatically, as long as a recent backup exists and someone reads the update emails. Since WordPress 5.5, administrators switch auto-updates on plugin by plugin in the Automatic Updates column of the Plugins screen, and theme by theme from the theme details under Appearance. By default WordPress runs these updates twice a day and emails the site owner when updates succeed or fail. Good candidates do one contained job, such as spam filtering or redirects, with nothing built on top of them.
Which updates should stay manual?
Keep an update manual when a bad release would stop sales, break every layout or break code written for you.
- WooCommerce and its payment, shipping and subscription extensions, which run the checkout.
- Page builders such as Elementor and their add-ons. Every page renders through them.
- Any plugin with custom code built on its functions or hooks. When those change, the custom code can fail.
- Major version jumps on any plugin, such as 4.x to 5.0.
What should you read before updating?
Read the changelog for every pending update. On the Plugins screen, the "View version" link under each update opens the plugin's details, and plugins from WordPress.org include a Changelog tab there. Look for:
- Security fixes: update soon, after a quick test.
- Words like breaking, removed, deprecated or renamed: test on staging first.
- A new minimum version of WordPress or PHP.
- A database update step: take a fresh backup and pick a quiet time.
The same window warns when a plugin has not been tested with your version of WordPress. That is not proof it will break, but it is a reason to test.
What does a safe update session look like?
One plugin at a time, staging first, with a fresh backup behind you. This is the order we work in:
- Take a fresh backup of files and database.
- Refresh the staging copy from live, so you test real plugins, settings and content.
- Update one plugin on staging, run the checks below, then move to the next. Bulk updates hide which plugin caused a problem.
- Note each plugin's old version number. You need it to roll back.
- Repeat the updates on live, in the same order, at a quiet time.
After each update, check what the business depends on:
- The homepage and your busiest pages, logged out.
- Every form: submit a test entry and confirm the email or CRM record arrives.
- On a store, a test order from cart to confirmation.
- The admin and the page builder editor still open.
- Tools > Site Health and the PHP error log show nothing new.
On sites with WP-CLI, the same routine looks like this:
# preview pending updates
wp plugin update --all --dry-run
# update one plugin, then check
wp plugin update your-plugin
# keep WooCommerce manual
wp plugin auto-updates disable woocommerceWhat if an update breaks the site?
Put back the previous version of the plugin that broke, and restore the full backup only if that fails. WordPress already helps in three ways:
- Since WordPress 5.2, a fatal error emails the admin a link to recovery mode, which pauses the broken plugin so you can log in and deactivate it.
- Since 6.3, if a manual plugin or theme update fails while installing, WordPress restores the previous version from a temporary backup.
- Since 6.6, after a plugin auto-update WordPress checks the homepage for a PHP fatal error. If it finds one, it rolls that plugin back to the previous version and emails the admin.
None of these notice a form that stops sending or a checkout that miscalculates. To roll back yourself, wp plugin install your-plugin --version=2.4.1 --force reinstalls a set version from WordPress.org, and each plugin's advanced page there offers Previous Versions. WordPress.org warns older versions may not be secure, so treat a rollback as a pause until a fix ships, with auto-updates off. For premium plugins, keep the previous zip from the vendor.
When should a plugin go?
When nobody maintains it, or nobody uses it. An abandoned plugin gets no security fixes, and a deactivated plugin is still code on your server. Site Health flags inactive plugins bluntly: "Inactive plugins are tempting targets for attackers."
On WordPress.org, two warnings matter. A plugin not tested with the latest 3 major releases of WordPress is flagged as possibly no longer maintained. A closed plugin can no longer be downloaded, and a security issue is one listed reason for closing. Find a maintained replacement, test it on staging, then delete the old plugin rather than leaving it switched off.
Where to start
List every plugin with its version, whether it auto-updates and what would break if it failed. Split the list into automatic and manual, delete what nobody uses, and book a regular slot for the manual ones. If an outdated plugin has already let someone in, start with our hacked WordPress cleanup checklist. If you would rather hand the routine over, our WordPress team handles updates, backups and plugin conflicts.
FAQ
Frequently asked questions
How often should we update WordPress plugins?
Security releases should go on soon, after a quick test on staging. Everything else can wait for a regular slot, weekly or every two weeks, so updates are grouped, tested one by one and checked together. Plugins on automatic updates still need someone to read the update emails and look at the site afterwards.
Do automatic plugin updates install the moment a release ships?
Not always. By default WordPress runs automatic updates twice a day. WordPress.org also lets plugin authors opt in to holding back automatic updates for the first 24 hours of a new release, on sites running WordPress 6.6 or later. Administrators can still install the update by hand during that window.
Can we bulk update every plugin at once?
You can, from Dashboard > Updates or the Plugins screen, and WordPress's own documentation recommends a quick review of the plugins first. We avoid bulk updates on live sites with WooCommerce, a page builder or custom code, because if something breaks you cannot tell which update caused it.
What should we do when an update email says something failed?
Open the site straight away and run your usual checks, then see which version the Plugins screen shows. On WordPress 6.6 or later, a plugin auto-update that caused a PHP fatal error on the homepage is rolled back. WordPress will try that update again at the next check, so switch auto-updates off for it until you know why.
Does deactivating a plugin delete its data?
Not in a well-built plugin. WordPress's plugin handbook says deactivation is for temporary tasks such as flushing caches, while removing options and tables belongs in the uninstall routine, which runs when you delete the plugin from the Plugins screen. Check what a plugin stores before you delete it, in case you need that data later.
Do we need a staging site for every update?
Not for every update. Small plugins on automatic updates can go straight to live with a recent backup in place. Anything on your manual list should go through staging first: WooCommerce, page builders, plugins with custom code built on them, and major version jumps. Refresh staging from live before each round so the test matches reality.


