The white screen of death is a WordPress error that is very common among WordPress users and has been a persistent problem haunting WordPress users since the platform was created. You, too, might be facing this error, but do not worry since below is everything you need to know about the WordPress white screen of death and how to fix it easily without much hassle. A concise and easy-to-understand guide has been provided below to understand better this error and the steps you need to follow to fix this.
What is the White Screen of Death?
The white screen of death in WordPress is an error that stems mostly from memory shortage. When the integrated script on your website exhausts the memory limit, this leads to an unresponsive script. Subsequently, that script gets killed by the WordPress hosting server or gets timed out. Thus, you do not see any error messages in most cases and are greeted by the WordPress white page, aka the screen of death.
Even though you would often see a white page, there are times when you will see a critical error message as well. This problem might be happening due to bad codes or plugins installed on your site, which leads to issues with your web hosting server. These cases can lead to a white screen and should be fixed promptly.
How can you fix this?
Here are some ways in which you can fix the WordPress white screen of death:
1. Debilitate Your WordPress Plugins
One of the least demanding and most normal ways to fix the WordPress WSoD is to debilitate all of your plugins. Regularly, a site goes down because of a terrible module update.
On the off chance that you can, in any case, get to your administrator region, a speedy method for doing this is to explore Plugins from the dashboard, select all plugins, and afterwards click on Deactivate from the Bulk Actions dropdown menu: This will hinder all of your plugins.
Assuming that fixes the issue, you’ll have to track down the offender. To do this, you can begin initiating the plugins individually, reloading the site later every enactment. When your front end goes down, you’ve found the acting up the module.
You would then connect with the module’s designer for help or post a help ticket in the WordPress Plugin Directory.
If you can’t log in to WordPress administrator, you can utilise a File Transfer Protocol (FTP) customer to access your site’s records registry.
Under the wp-content organiser of your root catalogue, find the plugins envelope. Rename it to something as per “plugins_old”:
Then, at that point, check your site again on the front end. Assuming this works, you should test each module individually. Rename your module envelope back to “plugins”, and afterwards exclusively rename each module organiser within it until you find the broken one.
2. Change to a Default WordPress Theme
Assuming the issue isn’t a module, your WordPress topic might be the reason for the White Screen of Death. You can supplant your subject by changing to a default one to check whether this is the issue.
If you can get to your administrator region, go to Appearance > Themes in your dashboard. Find and actuate a default WordPress topic like Twenty:
Then, at that point, test your site once more. If it works, you’ll realise the issue lies with your topic.
Assuming you can’t get to your dashboard, the cycle is equivalent to with plugins.
Use FTP to get to your site’s records and rename your wp-content/subjects envelope to something different:
WordPress will then, at that point, return to the most recent default topic, which is in all likelihood Twenty. On the off chance that you don’t have some other subjects, you can download one from the WordPress Theme Directory and afterwards transfer it to your topics organiser.
From that point forward, feel free to check your site once more. On the off chance that it works, maybe your topic has had a contention or a terrible update. If so, you may have to connect with the engineer for help or think about exchanging topics.
3. Clear Browser and WordPress Plugin Cache
If you approach the backend of your WordPress site, however, see the WSoD on the front end. It may very well be because of an issue with your store.
To fix it, take a stab at clearing your internet browser’s reserve and your WordPress storing module (expecting you have one introduced).
On the off chance that you have a storing module introduced on your WordPress site, for example, WP Rocket or WP Super Cache, most deal with a fast method for clearing the reserve through the module’s settings page.
Involving WP Super Cache, for instance, in your WordPress dashboard, you would explore Settings > WP Super Cache > Delete Cache:
4. Switch on Debugging Mode
If you see the WordPress White Screen of Death, the administrator region isn’t working, or you think you’ve tracked down the issue. However, you need to burrow further. You can empower investigating mode. This will show any blunders that are happening on your site.
To empower investigating, you’ll have to open the wp-config.php record of your WordPress introduction. Inside it, you should track down the accompanying line.
5. Increment Your Memory Limit
On the off chance that you see the feared WSoD void page in the wake of attempting a portion of the above arrangements, or you get a blunder griping about memory restricts or depleted memory, you’ll have to relegate more memory to the application.
This should be possible through the wp-config.php document on numerous WordPress introductions. Open the document and add the accompanying code:
define(‘WP_MEMORY_LIMIT’, ’64M’);
Assuming this doesn’t appear to work, you have a couple of choices. You can utilise your .htaccess document to build as far as possible in an ordinary climate. Essentially add the accompanying line:
php_value memory_limit 64M
Assuming you can’t get to your .htaccess record, you can utilise your php.ini document to expand as far as possible.
These are some ways in which you can fix this error.
Final Words
This is all there is to know about the WordPress white screen and how to fix that. Following the above steps can easily help you deal with this problem without any complications.
