Your association's Drupal site loaded fine yesterday. This morning, nothing—blank white page. No error message, no content, nothing. Members are calling. The board meeting is in two hours and you were planning to demo the new committee portal. The site just vanished.
The Drupal White Screen of Death (WSOD) is one of the most frustrating errors to encounter. Your association's website loads, but the page is completely blank—no error message, no content, nothing. Your members can't access their profiles, events, or renewal information. But despite its dramatic name, WSOD is usually fixable once you know where to look.
What Causes WSOD
A blank white page means PHP execution stopped before Drupal could render anything. The error happened before Drupal could even load—usually during PHP initialization or module loading. This is why you see no error message: PHP itself crashed before it could tell you what went wrong.
Common Causes
These are the patterns that typically lead to a blank white screen. We'll walk through diagnostics to isolate which one crashed your site.
- PHP memory limit exceeded — A complex operation (member data sync, AMS integration, large event registration form) exhausted available memory
- Fatal PHP error — A module or theme has broken code that causes an immediate crash
- Missing or corrupted module file — A module was partially uninstalled or a file got deleted
- Infinite loop or recursion — Custom code or a module is stuck in a loop that crashes PHP
- Disabled PHP functions — Your hosting provider disabled a function (like exec or shell_exec) that a module needs
- Server-level error — Web server misconfiguration or PHP crash at the hosting level
- Recent module update — A module updated to a version incompatible with your Drupal or PHP version
Step-by-Step Solutions
Step 1: Check Server Error Logs
The server logs will show the actual PHP error that caused the crash:
- Connect to your hosting account via SFTP
- Navigate to your Apache or Nginx error log (location varies by provider, usually /var/log/apache2/error.log or similar)
- Look at the most recent entries
- Common errors you'll see: "Allowed memory size exhausted," "Call to undefined function," "Parse error in /path/to/file.php"
If you don't have SFTP access or can't find the logs, contact your hosting provider and ask for the most recent error log entries from the time of the crash.
Step 2: Increase PHP Memory Limit
If the error mentions "memory exhausted," this is your fix:
- Open wp-config.php or settings.php (depending on your CMS) via SFTP
- Add this line near the top:
ini_set('memory_limit', '256M');
Save and test your site. If it loads, you've solved it. If you're already at 256M and it still fails, increase to 512M (though this might indicate a bigger problem).
Step 3: Disable Recently Updated Modules
If the WSOD started after a module update:
- Via SFTP, navigate to /sites/default/modules/
- Look for recently updated modules (check file modification dates)
- Rename the module folder to disable it (e.g., rename "custom_ams_sync" to "custom_ams_sync_disabled")
- Try loading your site
- If it loads, you've found the problem. Either downgrade the module or contact the module maintainer
- If it still fails, re-enable it and try the next module
Step 4: Check for Corrupted or Missing Files
If disabling modules doesn't help, a core file might be corrupted or deleted:
- Via SFTP, check that all files in /core/ exist and have recent modification dates
- If any are missing or very old, you may need to restore from a backup or reinstall Drupal core
- Check your /modules/ directory for incomplete installs (folders with no PHP files)
Step 5: Enable Error Reporting Temporarily
If you can access /sites/default/settings.php, add this at the bottom:
error_reporting(E_ALL);
ini_set('display_errors', TRUE);
Now reload your site. You should see the actual error message instead of a blank page. Once you fix it, remove these lines (they're a security risk in production).
Step 6: Restore from Backup (Last Resort)
If you can't find the problem and your site remains down:
- Contact your hosting provider and ask them to restore from the most recent backup before the WSOD started
- This will undo whatever change caused the crash
- Once restored, carefully apply updates and test each one
When to Call a Professional
Stop here if any of these apply. You need specialized expertise to proceed.
- The server error log shows a cryptic error you don't recognize
- You've tried increasing memory and disabling modules, and your site still shows WSOD
- You don't have access to SFTP or error logs
- Your association's member portal and event registration are completely down
- You need to restore from backup but don't have a recent one
Emergency Drupal Root Cause Identification and Restoration
If your association's Drupal site is showing a blank white screen and your team can't resolve it, contact us. We specialize in Drupal support for associations and can typically identify the root cause and restore your site. We'll give you a clear explanation of what crashed and how to stabilize it—plus guidance to prevent it next time.
Contact us and we'll prioritize root cause identification and restoration. Most WSOD cases are diagnosed within 4 hours.
Read our full emergency support or Contact us.