Updates help keep your website supported and address defects and security issues. They can also change behaviour, especially when several plugins depend on one another. This guide gives you a controlled workflow for WordPress core, plugin and theme updates. Follow the maintenance responsibilities agreed in your Digital Rebellion handover.
Establish who manages updates If Digital Rebellion handles updates under your service agreement, report notices and follow the agreed process. Avoid having several people update the same website independently. If you manage updates yourself, keep a simple record of what changed, when and how the main functions were checked.
Do not leave updates unattended indefinitely, but do not treat every promotional notice as a technical emergency. Read the source, version details and any compatibility or licence message. Paid extensions may need an active licence for access to updates.
Review the change before starting Check release notes for the components involved. Identify dependencies such as WooCommerce extensions, a page builder and its add-ons, or a theme with a companion plugin. There is no single correct update order for every website: follow vendor compatibility guidance and the tested plan for the site’s actual combination.
Major changes, database migrations and important store updates deserve testing on staging where available. Staging is a separate copy used for verification; it is not automatically private or safe to send customer emails from. Restrict access and isolate payment, email and external integrations appropriately.
- Review dependencies
- Verify backup and test plan
- Apply the tested updates
- Check forms and checkout
Confirm a usable backup Create a recent complete recovery point through the approved system and wait for confirmation. Know how to restore if dashboard access fails. For a busy store, account for orders and other activity that arrive after the backup; a full rollback can overwrite them.
Choose a suitable maintenance window for disruptive work. A backup reduces recovery risk but does not prove compatibility. Avoid starting a major update while a time-sensitive campaign or high-volume sales period is underway unless there is a clear operational reason.
Apply the planned updates Core updates are available through Dashboard → Updates when your permissions and hosting setup allow them. Plugin and theme screens also provide relevant update controls. Follow any vendor-specific prerequisites first.
Apply the tested set in a controlled sequence and wait for completion. Do not close the tab or repeatedly click an update while a process is active. If asked for unfamiliar server credentials, stop and have Digital Rebellion check the configuration rather than guessing or sharing passwords through a ticket.
Automatic updates can reduce delays, but the policy should reflect compatibility, monitoring and recovery capabilities. Review which components update automatically and who receives failure notices. Automatic operation still needs oversight.
Complete the post-update checks Open the website while logged out. Check the homepage, a service page, a blog post, navigation and mobile layout. Submit an approved test form and verify its notification. For stores, inspect a simple and variable product, cart, shipping calculation, coupon if relevant and the agreed test checkout.
Check that image loading, login and key integrations still work. A homepage that loads does not prove the store can accept orders. If WooCommerce requests a database update, follow its documented process and confirm completion rather than treating the first plugin-update message as the end of the task.
Handle a failure deliberately Record the error, affected URL, update time and versions changed. Avoid deactivating every live-store plugin as a first reaction. Digital Rebellion can investigate on staging or use a targeted rollback. Check for new orders and submissions before considering a database restore.
Frequently asked questions Can I update everything with one click? The button may exist, but batch updating makes it harder to isolate a failure. Use the tested approach for your website.
Should I delete inactive plugins? Review their purpose and dependencies first, then remove unneeded components through the agreed maintenance process.
