📝 You Raised the PHP Memory Limit Like Every Guide Says – the White Screen Is Still There
The White Screen of Death is one of WordPress’s most common failures, and the standard first-line fix – raising the PHP memory limit – is applied correctly and confirmed active, and the blank white page persists exactly as before, meaning the actual cause was never a memory limit in the first place.
🐞 The Problem
// wp-config.php
define('WP_MEMORY_LIMIT', '512M'); // raised generously
// Site: still a completely blank white page, no error text,
// no change at all after the memory limit increase.
🔍 Why This Happens
A White Screen of Death is WordPress's generic symptom for ANY uncaught PHP fatal error, and running out of memory is only ONE possible cause among many - a plugin/theme conflict, a corrupted core file, a PHP version incompatibility with a recently updated plugin, or a syntax error from a bad file edit can all produce the exact same blank white page. If memory genuinely wasn't the constraint, raising the limit changes nothing, since the real fatal error was never about running out of memory to begin with.
✅ The Fix: Turn On Error Display to See the Actual Underlying Error
- Enable WordPress debug logging first, safely (writes to a log file rather than displaying errors publicly on the live site): set
WP_DEBUGandWP_DEBUG_LOGto true in wp-config.php, then checkwp-content/debug.logfor the actual fatal error message and its exact file/line. - That specific error message tells you precisely what to do next – a plugin conflict points to deactivating that one plugin, a theme issue points to switching to a default theme temporarily, a corrupted core file points to re-uploading fresh WordPress core files.
- If access to wp-admin is also blocked by the white screen, rename the suspected plugin’s folder directly via FTP/file manager (this force-deactivates it without needing admin access) – a fast way to test the plugin-conflict theory even when the dashboard itself is unreachable.
⚠️ Why Raising Memory Is Still Worth Trying First, Just Not the Only Step
- It genuinely does fix a real subset of white screens (ones actually caused by a memory-hungry plugin or process) – it’s a reasonable first attempt, just not a complete diagnostic on its own when it doesn’t resolve things.
- Checking the actual PHP error log (not just WordPress’s own debug log) is worth doing in parallel – a truly fatal, uncatchable error sometimes shows there even when WordPress’s own logging doesn’t manage to capture it.
The White Screen of Death was never one specific bug — it’s WordPress’s blank response to any uncaught fatal error, and the memory limit fix only ever helps the one subset of causes that was actually about memory.
