How To Fix Common WordPress Error White Screen of Death 2022

Nothing is more frustrating than visiting your WordPress site and being greeted by the White Screen of Death (WoD). This issue prevents both administrators and visitors from accessing your website. Due to the absence of information pointing to a likely cause or cure, the WoD may be highly irritating. It is, nonetheless, one of the most prevalent WordPress mistakes. While this is troubling, it is usually resolvable.

We’ll go through what the WordPress WSoD is and what the most typical reasons are in this piece. Above all, we’ll guide you through nine different options for getting your site back up and running as quickly as possible. Let’s get this Fun started!

Free Shopify Website Solutions

Common WordPress Error White Screen of Death?

The WordPress White Screen of Death (also known as “WSoD”) occurs when, rather than the web page you’re attempting to view, you’re left with a blank white screen.

You may see various error messages depending on the browser you’re using. An HTTP 500 error message “This website isn’t functional and is unable to handle the request” is included in Google Chrome: 

• It’s simply a primary white screen, as you can see. There are no significant faults or warning signals in it.
• PHP code faults or memory limit depletion are usually the causes of the WordPress Common WordPress Error White Screen of Death.
• A malfunctioning theme or plugin is another possibility. If your website’s frontend is down, but your WordPress admin section is up, the latter is most likely the problem. Go to yourdomain.com/wp-admin to check whether your site’s dashboard is operational.

Gift for you: Get free website Consultancy

How to Fix WordPress White Screen of Death?

 

When you see the Common WordPress Error White Screen of Death, the first thing you’ll want to do is fix it as soon as possible. With that in mind, let’s look at nine different approaches you might use to fix the problem.

• WordPress Plugins Should Be Disabled
• Clear the Cache in your browser and your WordPress plugins.
• Enable Debugging Mode
• Expand Your Memory Capacity
• Check for Permissions Issues in Files
• Look for issues with failed auto-updates.
• Syntax Errors can be fixed, or a backup can be restored.
• Enhance PHP’s Text Processing Capabilities

Free Guidance: Activate a WordPress Default Theme

1 : Turn off all of your WordPress plugins

Disabling all of your plugins is one of the simplest and most popular ways to cure the WordPress  Common WordPress Error  WSoD. A botched plugin update is frequently the cause of a site’s downtime. If you still have access to your admin area, you may deactivate all of your plugins by going to Plugins from the dashboard, selecting all of them, and then clicking Deactivate from the Bulk Actions dropdown menu:

All of your plugins will be disabled as a result of this. If it solves the problem, you’ll need to figure out who’s to blame. To do so, begin by activating the plugins one at a time, refreshing the page after each one. You’ve discovered the misbehaving plugin when your front end goes down.

You can then contact the plugin’s creator or submit a support ticket to the WordPress Plugin Directory for assistance. If you can’t access WordPress admin, you can access your site’s files directory using a File Transfer Protocol (FTP) client. Locate the plugins folder in your root directory’s wp-content folder. Rename it to “plugins old” or anything similar:

Then, on the front end, double-check your site. If this works, you’ll need to go through and test each plugin individually. Rename your plugin folder to “plugins,” then rename each plugin folder inside it until you find the one that’s broken.

Last chance to boost your sales

2. Use the WordPress Default Theme

If the problem isn’t caused by a plugin, the White Screen of Death might be caused by your WordPress theme. You can swap your theme with a default one to determine whether this is the problem. Go to Appearance > Themes on your dashboard if you have access to your admin area. Choose a default WordPress theme, such as Twenty Twenty, and activate it:

After that, re-test your website. If it works, you’ll know your theme is the problem. If you can’t get into your dashboard, use the same steps as with plugins. To access the files on your site, use FTP and change the wp-content/themes folder to anything else: After that, WordPress will revert to the most recent default theme, which is almost certainly Twenty-Twenty. You may download a theme from the WordPress Theme Directory and then upload it to your themes folder if you don’t have any other themes.

After that, go ahead and double-check your website. If it works, it’s possible that your theme had a clash or received a poor update. If this is the case, you may need to seek assistance from the developer or switch themes.

3. Delete the cache files for your browser and WordPress plugins:

If you have access to your WordPress site’s backend but still see the WSoD on the frontend, it might be due to a caching problem. Try emptying your web browser’s Cache and your WordPress caching plugin to see if it helps (assuming you have one installed).

If you use a caching plugin like WP Rocket or WP Super Cache on your WordPress site, most of them provide a convenient option to clear the Cache from the plugin’s Settings page.

Using WP Super Cache as an example, go to Settings > WP Super Cache > Delete Cache: on your WordPress dashboard.

4. Switch on Debugging Mode

You may enable debugging mode if you’re still experiencing the WordPress White Screen of Death, the admin area isn’t working, or you think you’ve located the problem but want to dig deeper. This will display any issues that your website is experiencing.

You’ll need to access the wp-config.php file in your WordPress installation to allow debugging. You should find the following line within it:

• define( ‘WP_DEBUG’, false );

Replace “false” with “true” and refresh your page. You can add this line at the top of the file if it doesn’t already exist. You’ll get a white screen with some problem messages instead of the white screen. This isn’t a tremendous step forward, but it’s a start. The word error message should mention which file caused the problem, such as this:

• Cannot redeclare get_posts() (previously declared in 
• /var/www/HTML/WordPress/wp–includes/post.php:1874) in 
• /var/www/html/wordpress/wp–content/plugins/my–test–plugin/my–test–plugin.php on line 38

The fault occurs at line 38 of a plugin named my-test plugin, as you can see at the end of this sample message. As a result, removing the plugin should fix the problem.

You may need to contact your web host if you don’t observe any issues after enabling debug mode. It’s conceivable that your server’s debugging settings are incorrect.

5. Increase Your Memory Limit

 

If you’re still seeing the dreaded WSoD empty page after attempting some of the previous methods, or if you’re getting an error about memory limitations or depleted memory, you’ll need to give the program extra memory. On many WordPress installations, this may be done via the wp-config.php file. Add the following code to the file:

• define(‘WP_MEMORY_LIMIT’, ’64M’);

You have a couple of choices if this doesn’t appear to work. In a normal setting, you can increase the RAM limit by editing yours. ht-access file. Add the following at the end of the line:

php_value memory_limit 64M

If you’re still running out of memory and need to assign more, there might be a problem with your program. Maybe your theme or one of your plugins is using all of your resources.

You might want to hire a developer to take a look at this stage. Even your host may be able to assist you by providing you with your site’s SQL logs and other resource statistics.

6. 
   

   Check File Permission Issues

Permission and ownership difficulties are other possible sources of the WSoD. This is an issue that you can solve on your own. However, unless you’re sure you know what you’re doing, we wouldn’t recommend it since you can unintentionally create weaknesses that attackers might exploit.

There are three easy guidelines to follow when it comes to WordPress permissions:

664 or 644 should be used for all files. The default setting for folders should be 775 or 755.

• 660, 600, or 644 should be specified in the wp-config.php file.

If you have SSH access to your server, execute the following command from the root WordPress directory to apply the relevant rules:

• sudo, find. -type f -exec ch-mod 664 {} +
• sudo, find. -typed -exec ch-mod 775 {} +
• sudo ch-mod 660 wp-config.php

If you are unsure how to do this or are a bit intimidated, go ahead and ask your web host for help.

7. 
   

   Check for Failed Auto-Update Issues

Sometimes WordPress runs into difficulty with updates, such as when the server times out. More frequently than not, this problem fixes itself automatically. However, in certain rare circumstances, it may lead to the WordPress White Screen of Death.

The first thing you should do is go into your WordPress root directory and see whether there’s a .maintenance file there (the file’s name may be truncated as well). What you’d want to do is try removing that file and loading up your site again. If the upgrade was completed, but WordPress fails to delete this file automatically, everything should go back to normal. Sometimes WordPress runs into difficulty with updates, such as when the server times out. More frequently than not, this problem fixes itself automatically. However, in certain rare circumstances, it may lead to the WordPress White Screen of Death.

The first thing you should do is go into your WordPress root directory and see whether there’s a .maintenance file there (the file’s name may be truncated as well).

What you’d want to do is try removing that file and loading up your site again.

If the upgrade was completed, but WordPress fails to delete this file automatically, everything should go back to normal.

8. Resolve Syntax Errors or Restore a Backup

Another typical cause for the WordPress WSoD is when you’re modifying the code on your WordPress site and accidentally mistyping something or using improper syntax. One character in the incorrect place might take down your entire site, which is why you should never alter code on your live production site.

Not to worry, though. You may always access your site through FTP and undo the update you made manually. If you don’t know what update triggered the problem, this is where having WordPress backups in place comes in helpful. Keep in mind that if you selected debug mode in WordPress before, there could also be an error message suggesting a parse syntax issue. If this is the case, it should inform you exactly where to discover the issue code.

9. Increase the PHP Text Processing Capability

At this point, if the WSoD has not yet been addressed, there’s one other method you may attempt. In rare circumstances, this problem could arise because a page or message is highly long.

If this is the case, you can try modifying the PHP text processing capabilities on your site by increasing the backtrack and recursion limitations. To do so, paste the following code into your wp-config.php file:

• /* Trick for long posts /
• ini_set(‘pcre.recursion_limit’,20000000);
• ini_set(‘pcre.backtrack_limit’,10000000);

Ending Words

The WordPress White Screen of Death may be immensely annoying, even scary. Various things can go wrong, but happily, the situation is typically not as awful as it looks.

A quick plugin and theme check should cure the WSoD issue in most circumstances. Getting more familiar with WordPress debug mode can undoubtedly throw more light on the problem and help you.

If you’ve experienced any additional WordPress White Screen of Death instances, let us know so we can learn from them and share the experience!