DroxinHosting & Repair
WordPress

WordPress Editor or Dashboard Blank White Screen: How to Fix It

  • October 28, 2026
  • 160 views
  • Droxin repair team
WordPress Editor or Dashboard Blank White Screen: How to Fix It

Sometimes the public site loads fine, but wp-admin, the post editor or a WooCommerce screen is completely white. This is a white screen of death that only hits the admin side, and it has different causes from a site-wide one. Here is how to find which one you have. If the whole site is blank, start with our white screen of death guide instead.

Find out what kind of white screen it is

  • The whole dashboard is white (also after login): a PHP fatal error that only runs in the admin. Usually a plugin or the memory limit.
  • The dashboard works, but "Edit Post" is white: the block editor (Gutenberg) is a JavaScript app. A white editor almost always means a script failed to load or crashed.
  • Only WooCommerce pages are white (Orders, Products, Settings): a WooCommerce extension or a memory limit on large stores.
  • White screen and no errors anywhere: errors are hidden. Turn on logging (next step) before changing anything.

1. See the real error

A white screen hides an error, it doesn't mean there is none. In wp-config.php replace define( 'WP_DEBUG', false ); with:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Open the white page once, then read /wp-content/debug.log. The last PHP Fatal error line names the file and line, and the folder in its path (/plugins/name/) names the plugin. For the editor, also press F12 in the browser and look at the Console tab: a red error there names the script that failed.

2. Raise the admin memory limit

The admin uses more memory than the front end, and large WooCommerce stores, page builders and SEO plugins can run it out. If the log says "Allowed memory size of ... bytes exhausted", add above "That's all, stop editing!":

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

WP_MAX_MEMORY_LIMIT is the one the admin uses. If nothing changes, your host caps PHP memory lower: raise memory_limit in cPanel's MultiPHP INI Editor or ask the host.

3. Disable the plugin that crashes

You can't reach the Plugins screen, so do it with File Manager or FTP: in /wp-content/plugins/ rename the plugin's folder (for example wordfence to wordfence-off). WordPress deactivates it and keeps its settings. If the log didn't name one, rename the whole plugins folder to plugins-off, check the admin loads, rename it back, and then turn plugins back on one at a time from the dashboard until the white screen returns.

4. Fixing a white post editor

  • Caching or minify plugins that combine admin scripts break the editor. Exclude /wp-admin/ from minification, or turn the option off and clear the cache.
  • A CDN or Cloudflare Rocket Loader rewriting scripts: disable Rocket Loader for the admin, or add a page rule that bypasses /wp-admin/*.
  • Browser extensions (ad blockers, script blockers): test in a private window with extensions off.
  • A plugin that adds editor blocks after an update: the console error names it; update or deactivate it.
  • Add define( 'CONCATENATE_SCRIPTS', false ); to wp-config.php: if that fixes it, the server is cutting off the combined script file.

5. WooCommerce admin pages are white

Check the log for the extension named in the fatal error (payment, shipping and subscription add-ons are the usual ones) and update or disable it. On big stores the Orders screen can also time out: raise max_execution_time to 120 and the memory limit as above, and enable WooCommerce's High-Performance Order Storage if your extensions support it.

Text is white or invisible in the editor

If the editor loads but your text is white on a white background (or the whole post looks empty until you select it), the content is there — only its colours are wrong. Usual causes:

  • A dark-mode browser extension such as Dark Reader recolouring the editor. Turn it off for your site and reload.
  • The theme's editor styles made for a dark site: the theme tells the editor to use white text, but the editor background stays white. In a block theme, check Appearance → Editor → Styles → Colors; in a classic theme, the theme's editor-style.css. Switching to a default theme for a minute confirms it.
  • Custom CSS added to the admin by a plugin or snippet, often with color: #fff on the editor area.

To see and copy your text meanwhile, open Options (⋮) → Code editor (Ctrl+Shift+Alt+M).

Only one post or page is blank in the editor

When every other post opens but one stays white, that post usually holds a block the editor can't render — often from a plugin you have since deactivated, or HTML pasted from somewhere else. Open it in the code editor, look for the block named in the browser console error, and remove or fix it; for a block marked "This block contains unexpected or invalid content", use Attempt block recovery. Reactivating the plugin that created the block also brings it back.

"Updating failed" or "The response is not a valid JSON response"

The editor saves through the WordPress REST API (/wp-json/). When saving fails with this message, something is blocking or breaking that request:

  • A security plugin or firewall (Wordfence, ModSecurity on the host, Cloudflare WAF rules) blocking /wp-json/ — check its log and allow the request.
  • Permalinks out of sync — open Settings → Permalinks and click Save Changes once.
  • The site address set to http:// while the site runs on https:// — fix it in Settings → General.
  • A PHP warning printed before the response — it breaks the JSON; the debug log from step 1 shows it.

Tools → Site Health also tests the REST API and tells you when it is blocked.

When you are done

Set WP_DEBUG back to false and delete debug.log: it can contain file paths and should not stay public.

If the log is full of errors you don't recognise, or you can't get into the admin at all, we fix admin and editor white screens at a fixed price: free diagnosis, a backup first, and you pay only after you have checked that everything works.

Is your website having a similar issue?

We diagnose and fix it within 24 hours — you only pay after the fix is confirmed.

Get a Free Diagnosis

More from the blog