Magento How to debug blank white screen

Magento How to debug blank white screen

July 22, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento How to debug blank white screen

Debugging Magento Blank White Screens: A Comprehensive Guide

A blank white screen (WSOD) or “white screen of death” is one of the most common issues faced by Magento developers. It typically occurs when an error is encountered during page rendering, causing the browser to display a completely blank page without any content.

In your case, you have already taken several important steps:

  • Enabled developer mode in Magento
  • Set errors to ‘on’ in the admin panel
  • Configured proper permissions for the var/logs/ directory
  • Added ini_set('display_errors', 1) to index.php

However, despite these configurations, no errors are being logged or displayed. This can be quite frustrating, as it makes troubleshooting almost impossible.

Understanding the Magento Error Handling Process

Before diving into potential solutions, let’s understand how Magento handles errors:

  • When an error is encountered during page rendering, Magento typically tries to log the error in the var/log/ directory.
  • If logging fails (e.g., due to permission issues or incorrect configuration), the error will still be caught by PHP and sent to the php.ini error handler.
  • The php.ini error handler can either display the error directly on the page, write it to an error log file, or ignore it.

Troubleshooting the Error Logging Issue

1. Checking PHP Error Handling Configuration

Ensure that your php.ini configuration allows errors to be displayed or logged:

display_errors = On
log_errors = On
error_log = /var/log/php-fpm.log

Replace /var/log/php-fpm.log with the actual path where you want to log PHP errors.

2. Verifying Error Reporting Levels

In your index.php, make sure the error reporting level is set correctly. For development, you should have:

ini_set('display_errors', 1);
error_reporting(E_ALL | E_STRICT);

3. Enabling Xdebug

If the above steps don’t work, consider using an external debugging tool like Xdebug. Xdebug allows you to pause execution of your script and inspect variables.

To enable Xdebug:

  • Install it via PECL or your package manager.
  • Add the following configuration in your php.ini file:
zend_extension=xdebug.so
xdebug.remote_enable=1
xdebug.remote_handler="dbgp"
xdebug.remote_port=9003

4. Checking for Memory Limitations

If you’re still experiencing issues, a common culprit is memory limitations. Magento can sometimes require more memory than the default PHP configuration provides.

You can increase the memory limit in your php.ini file:

memory_limit = 2G

Conclusion: Persisting With Debugging Efforts

Debugging WSOD errors in Magento requires a systematic approach and patience, as there can be multiple points of failure. Always start with the basics—check permissions, verify configurations, and ensure that all necessary tools are enabled.

If you’ve tried the steps outlined above without success, consider reaching out to the Magento community or a professional development service like Laravel Company for further assistance.

Remember, the key is to persist with your debugging efforts until you identify the root cause of the issue. With the right tools and approaches, even the most stubborn WSOD errors can be resolved.

Stay patient, keep learning, and happy coding!

Security Admin Configuration Import/Export

Our network