Start with the administrator’s recovery email and the exact error. If it identifies a plugin, temporarily deactivate that component and check the public site. Restoring access is the first step; you still need to resolve the incompatibility and verify the features that depended on it.
Record what changed before trying another fix
Write down the plugin name, its old and new versions if known, the update time and which pages fail. Include any theme, PHP or hosting change made at the same time. An error immediately after an update makes that update worth investigating, but does not establish the cause on its own.
Keep the exact error text and ask the host for the relevant PHP error log if you cannot see it. Before changing files, preserve the current files and database where possible. Also identify the most recent usable backup from before the update. These serve different purposes: one preserves the failing state; the other may provide a recovery route.
Check the WordPress recovery email
Look in the site administrator’s mailbox and spam folder for the WordPress technical-issue email. If it contains a Recovery Mode link, use that link to sign in and read the notice identifying the plugin or theme that failed. Keep the link private.
Recovery Mode can pause a faulty component for your administrator session. That does not mean ordinary visitors have a working website. Deactivate the identified plugin if appropriate, then test the public page outside that session. Not every failure produces a usable recovery email.
If you cannot reach the dashboard
Your host can help locate the error and temporarily disable the implicated plugin. If you are comfortable with SFTP or the hosting file manager, WordPress also documents temporarily renaming an individual plugin folder under wp-content/plugins. Record its original name before changing it.
Deactivation can remove forms, checkout or other important functionality. Avoid deleting the plugin or changing the database as an initial experiment. If the error does not identify a component, request help with diagnosis rather than switching off unrelated parts of a live business site.
Choose a repair with a recovery plan
Use the error and the plugin vendor’s guidance to decide whether the next step is a corrected release, a compatibility change or a temporary rollback. Test the proposed change on a separate staging copy when available. Do not assume an older release is a permanent solution, particularly if the update addressed a security issue.
Before restoring an older database, account for enquiries, orders and edits received since that backup. A full restore can replace newer records. Agree how to preserve them before treating the restore as a quick fix.
Check the business functions, not just the homepage
Record the final versions and what was tested. If the plugin must remain disabled, make that limitation visible to whoever relies on it. A page that loads while its enquiry form is missing is only a partial recovery.
- Load the affected page as a logged-out visitor.
- Check login and the features supplied by the affected plugin.
- Submit a test enquiry and confirm that its notification arrives.
- If the site sells online, test the agreed checkout journey without charging a real customer.
- Review the relevant error log for fresh failures after the test.
Explore one-time WordPress fixes.
Official references
Use these references alongside the checks and questions in this guide. Interfaces and provider requirements can change.