A plugin update broke the website. What next?
A failure immediately after an update is a useful clue, not complete proof. There may be a compatibility problem with the theme, another plugin or the server version. Reproduce the fault with as few changes as possible and restore the affected function without losing recent information.
Record the before and after
Note the updated component, previous and current versions, and when the fault began. Describe what stopped working: administration, payment, navigation or one page. Collect the error message and other changes made in the same window. When several updates happened together, do not select a culprit merely because it is the last one you remember.
Protect the current state
Before restoring an older copy, check enquiries, orders and content created since that backup. A test copy lets you investigate without interrupting the public website again. WordPress documents plugin deactivation as part of troubleshooting, but on a working shop it can remove essential functions. Plan the test and recovery path.
- Confirm a backup of both files and database.
- List functions that depend on the suspected component.
- Reproduce the same error on the test copy.
- Record each change and its result, including unsuccessful attempts.
Separate recovery from a lasting fix
Returning to an earlier version may restore service during investigation, but does not necessarily explain the incompatibility. Compare requirements, logs and vendor information. If a component is no longer maintained, assess replacement and configuration migration. Do not keep an outdated version indefinitely simply because the homepage loads again.
Validate the complete journey
Before closing the work, test the steps that generate revenue or enquiries, including sent messages and administrative records. Check mobile pages and anonymous visits. Document the identified cause, applied version and next update procedure. That record turns an emergency into a concrete improvement to maintenance.
Frequently asked questions
Should I disable every automatic update?
The decision depends on your components and ability to test and recover. Set a maintenance policy covering ownership, backups and monitoring relevant updates.
Will deactivating a plugin remove data?
Behaviour varies by plugin, and deactivating differs from uninstalling. Consult its documentation and confirm a data backup before acting.
Reference documentation
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements