WordPress White Screen After Plugin Update Checklist

halfbrain_logo512adminJune 12, 2026
12 lượt xem

WordPress White Screen After Plugin Update Checklist

A white screen after a plugin update usually means WordPress hit a fatal PHP error. The site may show a blank page, wp-admin may stop loading or only some pages may fail. This checklist helps you recover without making the situation worse.

Common causes

  • Plugin update is incompatible with your PHP version.
  • Plugin conflicts with another plugin.
  • Theme conflict.
  • Memory limit is too low.
  • Cached files conflict with new plugin code.
  • Fatal PHP error stops page rendering.

Checklist

  1. Do not keep refreshing and changing settings randomly.
  2. Check if wp-admin still works.
  3. Check Nginx and PHP error logs.
  4. Identify the last plugin updated.
  5. Disable the suspected plugin through file manager or SSH if wp-admin is inaccessible.
  6. Clear cache after disabling the plugin.
  7. Check PHP version compatibility.
  8. Restore backup if disabling the plugin is not enough.
  9. Update in staging next time if the site is important.
  10. Document the plugin version that caused the issue.

Final check

The goal is to restore access first, then investigate compatibility. Do not update more plugins while the site is already broken.

Checklist Type Troubleshooting
Level Beginner
Risk Level High Risk
Estimated Time 20–60 minutes

When to Use This Checklist

Use this checklist when WordPress shows a blank page or white screen after updating a plugin.

Required Tools

WordPress admin access if available, SSH or file manager, backup, Nginx log, PHP error log, cache plugin access

Before You Start

Stop making new changes until you identify the plugin or error that caused the white screen.

Verification Steps

  1. Homepage loads.
  2. wp-admin loads.
  3. Error log stops showing fatal errors.
  4. Core pages work.
  5. Cache is cleared.

Rollback Plan

If the site remains broken after disabling the plugin, restore the latest clean backup or switch to a default theme temporarily to isolate the issue.

Common Mistakes

  • Updating more plugins after the site breaks.
  • Deleting plugin data before backup.
  • Ignoring PHP fatal error logs.
  • Clearing cache before identifying the cause.
  • No backup before plugin updates.

Related Commands

sudo tail -n 100 /var/log/nginx/error.log
cd /var/www/example.com/wp-content/plugins
mv plugin-folder plugin-folder-disabled
wp plugin list

Share:

Disclaimer: The guides, checklists, commands, and examples on HalfBrain.net are provided for educational and operational reference only. Server environments, hosting providers, software versions, security settings, and WordPress configurations can vary, so you should always review commands before running them on your own system. We do our best to keep the content accurate and useful, but we cannot guarantee that every command, configuration, or recommendation will fit every environment. Always back up your website, database, and server configuration before making changes. HalfBrain.net is not responsible for data loss, downtime, security incidents, misconfiguration, or other issues that may result from applying the information on this website. Use the material at your own discretion.

Leave a Reply

Your email address will not be published. Required fields are marked *