{"id":20396,"date":"2026-11-02T12:25:42","date_gmt":"2026-11-02T11:25:42","guid":{"rendered":"https:\/\/stage.surver.nl\/kennisbank\/wordpress-update-mislukt-oplossen\/"},"modified":"2026-11-03T14:54:05","modified_gmt":"2026-11-03T13:54:05","slug":"how-to-fix-a-failed-wordpress-update","status":"publish","type":"kennisbank","link":"https:\/\/stage.surver.nl\/en\/kennisbank\/wordpress-update-mislukt-oplossen\/","title":{"rendered":"Website Down After a WordPress Update: Here's How to Fix It"},"content":{"rendered":"
\"Website<\/figure>\n\n\n\n

Click on Update Everything<\/strong>, or you might get an email in the morning saying that something was automatically updated, and now you see an error message or a blank page. If your site stops working after an update, disable the most recently updated plugin or theme via FTP or the hosting control panel by renaming the folder. If that doesn\u2019t work, restore the backup from before the update. Your site is almost never truly gone, because your content is still in the database. Below, you can read what I do when a WordPress update fails, from the simplest to the most involved steps. This article is part of WordPress Management: The Complete Guide<\/a>.<\/p>\n\n\n\n

What will you see after the update?<\/h2>\n\n\n\n

An update usually breaks your site because a new version of a plugin, theme, WordPress core, or PHP is no longer compatible with the rest of your installation. What you see already tells you a lot about where to look for that incompatibility.<\/p>\n\n\n\n

What do you see?<\/th>Usually means<\/th>Read more<\/th><\/tr><\/thead>
\u201cA critical error has occurred on this site\u201d<\/td>PHP error in a plugin or theme<\/td>A critical error has occurred<\/a><\/td><\/tr>
A blank, white page<\/td>Fatal error without notification<\/td>white screen of death<\/a><\/td><\/tr>
\u201cTemporarily unavailable due to scheduled maintenance\u201d<\/td>Update Stopped Midway<\/td>stuck in maintenance mode<\/a><\/td><\/tr>
The plugin works only partially, or the update stops<\/td>Incomplete update<\/td>Re-upload the plugin or wp plugin install plugin-name --force<\/code><\/td><\/tr>
Site works, but the layout is broken<\/td>Cache of Page Builder CSS<\/td>First clear the cache<\/a><\/td><\/tr>
Checkout or form is not working<\/td>Plugin conflict in a single function<\/td>How to Update WooCommerce Without Breaking Your Checkout<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

No matter what the symptom is, the recovery steps below remain the same.<\/p>\n\n\n\n

Step 1: Find out which update it was<\/h2>\n\n\n\n

The fastest way to find the cause is to check what was last updated. The first thing I check is the inbox of the administrator\u2019s email address. When a fatal error occurs, WordPress sends an email saying something like \u201cYour site has a technical problem,\u201d and it often specifies exactly which plugin or theme caused the error. If you can still log in, check under Plugins<\/strong> which plugins have recently been updated.<\/p>\n\n\n\n

If that doesn't provide a clear answer, I'll check the error log. On most servers, there's a file error_log<\/code> in the folder where the error occurs. In the error message, you'll see a path like wp-content\/plugins\/plugin-name\/<\/code>, and that folder name is your suspect. If there's no log, turn on debug mode. First, make a copy of wp-config.php<\/code> and place the lines above the comment line that says you should stop editing. Place WP_DEBUG<\/code> and WP_DEBUG_LOG<\/code> on true<\/code> and WP_DEBUG_DISPLAY<\/code> on false<\/code>, so that your visitors won't see the error messages. The errors will then appear in wp-content\/debug.log<\/code>. Turn it off again when you're done. For more information, see Enable debug mode<\/a>.<\/p>\n\n\n\n

Step 2: Disable the plugin or theme<\/h2>\n\n\n\n

To disable a plugin without access to the admin panel, simply rename the folder. Think of it like a blown fuse. You don\u2019t reset the power for the whole house to yesterday\u2019s settings; instead, you find the device that caused the short circuit and unplug it.<\/p>\n\n\n\n

    \n
  1. Can you still log in, or do you have the recovery mode link from the email? If so, just deactivate the plugin via Plugins<\/strong>.<\/li>\n\n
  2. Can't access it? Open the file manager in your hosting control panel or connect via (S)FTP.<\/li>\n\n
  3. Go to wp-content\/plugins\/<\/code> and rename the folder containing the suspect plugin, for example, to plugin-name-off<\/code>. WordPress will then disable it.<\/li>\n\n
  4. Not sure which one it is? Rename the entire folder. plugins<\/code>, put it back, and activate the plugins one by one.<\/li>\n\n
  5. Was it a theme update? Rename the theme folder, and WordPress will fall back to an installed default theme, such as Twenty Twenty-Five.<\/li>\n\n
  6. Clear the cache\u2014for example, in LiteSpeed Cache\u2014and check the site.<\/li>\n<\/ol>\n\n\n\n

    At the command line, type wp plugin deactivate plugin-name<\/code> The same applies to WP-CLI. Always keep a default theme installed; otherwise, WordPress won't have anything to fall back on.<\/p>\n\n\n\n

    Step 3: Roll back\u2014first that one update, and only then make a backup<\/h2>\n\n\n\n

    Disabling a feature is a last resort, because most of the time you\u2019ll want it back. Don\u2019t reach for the backup right away. Usually, just one plugin is the culprit, and with a full backup, you\u2019ll throw away everything that\u2019s happened since then.<\/p>\n\n\n\n

    Restore a single plugin or theme<\/h3>\n\n\n\n

    For plugins and themes from the official WordPress repository, use WP Rollback. To restore a premium plugin, download the previous version as a ZIP file and upload it via Plugins > New Plugin > Upload Plugin<\/strong>, then select \"Replace.\" Sometimes WordPress has already taken care of it. Since version 6.3, it automatically reverts a failed manual update of a plugin or theme, and since 6.6, it also reverts an automatic plugin update that results in a fatal error. If the issue is related to PHP, temporarily switch to a different version cPanel > Select PHP Version<\/strong> and read Update PHP Version<\/a>. It's rarely necessary to restore WordPress core itself. If you do need to, you can do so using the WP Downgrade plugin or by modifying the folders wp-admin<\/code> and wp-includes<\/code> to replace it, and only temporarily.<\/p>\n\n\n\n

    Restoring a Full Backup<\/h3>\n\n\n\n

    Restoring a backup is the right choice if you can\u2019t figure out what\u2019s broken, if multiple things are broken at the same time, or if the update modified your database. Just be aware that orders, form submissions, comments, and posts made after the backup was taken will be lost. For a WooCommerce online store, I therefore first export the new orders or restore only the files. When Managed WordPress Hosting<\/a> You do this from the hosting control panel, but the current state isn't automatically saved, so be sure to make a backup yourself first. You can find instructions on how it works in Restore a backup<\/a>. For minor errors on a page, there is undo changes<\/a>.<\/p>\n\n\n\n

    After Recovery: Prevent It From Happening Again<\/h2>\n\n\n\n

    Disabling or reverting a plugin is a temporary solution, not a permanent fix. If you leave it that way, you\u2019ll miss out on security updates. Check the changelog or the support forum to see if the issue is known, and wait for a fix. Test the new version first on a staging environment<\/a> and in the meantime, put Turn automatic updates on or off<\/a> for that plugin only. If a plugin is no longer being updated, replace it with an alternative. You can find out how to choose one in the Guide to Plugins and Themes<\/a>. In addition, I always work on things one at a time instead of all at once, and I make a backup beforehand. How to set up those backups is explained in the Guide to Backup and Migration<\/a>. That way, you'll know right away which update is causing the problem. If you have an online store, test the checkout process after every update, or leave that to WooCommerce Management<\/a>.<\/p>\n\n\n\n

    With our shared hosting plans, you have everything you need to resolve this on your own. cPanel includes File Manager, SSH, and WP-CLI, so you can rename a plugin folder without needing a separate FTP program. You can restore a backup for free using JetBackup 5\u2014either for files or databases\u2014and you can create a staging environment by cloning your installation in Installatron. If you\u2019re on Surver Cloud, please contact support. If you\u2019d rather not handle this yourself, Surver will restore the site within WordPress Management<\/a> and from now on, we'll perform the updates for you every month. Read more Updating WordPress Safely<\/a> and the maintenance checklist<\/a>.<\/p>\n\n\n\n

    Frequently Asked Questions<\/h2>\n\n\n\n

    I'm not receiving a recovery mode email. What should I do?<\/strong><\/p>\n\n\n\n

    First, check your spam folder and make sure the administrator's email address is listed under Settings > General<\/strong> is still correct. If you can't access the admin panel, rename the plugin folder using File Manager or FTP as described in step 2.<\/p>\n\n\n\n

    My site keeps showing \u201cTemporarily unavailable due to scheduled maintenance.\u201d What should I do?<\/strong><\/p>\n\n\n\n

    Delete the file .maintenance<\/code> in the root directory of your WordPress installation. That file is left behind if an update stops halfway through. I'll cover other messages that appear after an update in Troubleshooting WordPress Errors<\/a>.<\/p>\n\n\n\n

    Can Surver restore my site after a failed update?<\/strong><\/p>\n\n\n\n

    Yes, Surver does that as part of the maintenance subscription. As a hosting customer, you can also restore a backup yourself at no cost using JetBackup 5 in cPanel. If you have any questions, please email our support team.<\/p>","protected":false},"excerpt":{"rendered":"

    Je klikt op Alles bijwerken, of je krijgt ’s ochtends een mail dat er automatisch iets is bijgewerkt, en nu zie je een foutmelding of een lege pagina. Werkt je site niet meer na een update, schakel dan via FTP of het hostingpaneel de laatst bijgewerkte plugin of het thema uit door de map te […]<\/p>\n","protected":false},"author":2,"featured_media":20527,"template":"","kennisbank_categorieen":[62],"class_list":["post-20396","kennisbank","type-kennisbank","status-publish","has-post-thumbnail","hentry","kennisbank_categorieen-wordpress"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank\/20396","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank"}],"about":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/types\/kennisbank"}],"author":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/users\/2"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media\/20527"}],"wp:attachment":[{"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/media?parent=20396"}],"wp:term":[{"taxonomy":"kennisbank_categorieen","embeddable":true,"href":"https:\/\/stage.surver.nl\/en\/wp-json\/wp\/v2\/kennisbank_categorieen?post=20396"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}