Separate an incomplete update from a problem that appears afterwards
You updated WordPress, a theme or a plugin and the website no longer works as expected. First establish whether the update failed to complete or finished before a problem appeared. The necessary checks may differ.
An incomplete update may show a failure message or a maintenance screen that remains visible. After a completed update, the website may open while its form, menu or checkout fails. Alternatively, the whole website or only its administration area may become inaccessible.
Record exactly what you see and when it began. A problem following an update is a reason to investigate the change, not proof that a particular plugin caused it or that everything needs reinstalling.
If the message reports an error 500, the WordPress error 500 guide explains what it means and how the logs and recent change can guide a fix.
Preserve the current state and avoid piling up changes
Before clicking Update again, deleting components or restoring an earlier version, contact the people maintaining the website. Several people making changes at once makes it harder to establish what happened and choose a recovery approach.
Keep the error message, approximate time and last known working behaviour. If the website is still receiving orders or enquiries, that new information must be considered before restoring a backup.
The official WordPress updating guide recommends preparing file and database backups before updating. If their status is unclear, ask the team rather than assuming a rollback would preserve recent data.
Prepare a short incident record
| Item | Record | Useful detail |
|---|---|---|
| Change | What was updated and when. | WordPress, theme or plugins; versions if available. |
| Outcome | Completion or a reported failure. | Exact message or maintenance screen. |
| Affected areas | What works and what does not. | Homepage visible; form does not submit. |
| Last working state | When the function last worked. | Time and journey checked. |
| Recent information | Changes since the latest backup. | Orders, enquiries or content changes. |
| Coordination | Who is investigating and what has been tried. | Responsible person, actions and outcomes. |
Remove personal information and secrets from screenshots. The record does not need passwords or complete log files: identify where evidence is retained and who can access it with authorisation.
If the update did not finish, have the technical team review the process
Share the exact notice and whether you can access the administration area. The team should check the installation’s actual state and available records before resuming or completing the process.
A message may point towards file access, a download or a resource limit. These possibilities need checking in that environment; they are not reasons to change permissions or increase memory automatically. No single setting fixes every failed update.
WordPress documents failed update situations, but applying one instruction does not establish that the installation is complete. Removing a maintenance notice does not establish that the website works properly either.
If it finished but something fails, identify the affected function
Describe a short journey: open a page, press the menu button or complete the contact form. Explain the expected result and what actually happens. Agree a test procedure with your team that avoids real purchases, charges or messages to customers.
The team can compare versions and dependencies in a test copy and inspect its records. WordPress debugging documentation distinguishes recording errors from displaying them. Do not enable technical notices for visitors or publish diagnostic files yourself.
If only email notifications are missing, use the specific form and email delivery checks. A correct-looking design does not establish that notifications or external connections work.
Agree the recovery approach and its checks
Depending on the findings, the team may consider correcting a setting, completing the update or recovering a compatible version. Before doing so, establish which information must be preserved and which tests will demonstrate the required recovery.
The backup and recovery worksheet helps organise those conditions. Restoring an older version may affect later changes; it should not become a permanent decision to leave components unmaintained.
Fictional example: after a booking component is updated, the homepage still opens but its calendar does not load. Checking only the homepage would not validate recovery: the calendar and booking journey need testing with the procedure prepared by the team.
When closing the incident, retain the changes made, functions checked and outstanding work. That record will help with the next update.
Use what you learned to prepare the next update
Agree the required backup, where significant changes will be tested and which functions will be checked afterwards. If a component’s future is uncertain, review its support and alternatives rather than repeatedly applying an unreviewed temporary fix.
If you need help, tell us what happened when you updated WordPress. We can discuss the situation, necessary work and timeframe with you. For immediate attention, follow the incident procedure agreed with your technical owner or the emergency service you have contracted. Nodo91 can assess a scoped intervention; we do not provide emergency resolution.