WordPress White Screen of Death solution

WordPress White Screen of Death

WordPress White Screen of Death solution, Nothing is more hurtful than browsing to your WordPress website and suddenly being met with the white screen of death, making it unavailable to both administrators and visitors. Now we are going to lead you through six common issues that mostly arise with the WordPress white screen of death, the common causes, and most importantly, by following these solutions, you can get your site back up and running as fast as possible.

WordPress White Screen of Death

white screen of death mostly caused by Hypertext Preprocessor (PHP) code errors or memory limit exhaustion. The primary thing you should do is determine whether or not the admin on your site is working. If the website is down, but the WordPress admin is working, possibilities are you have a faulty theme or plugin. You can check your admin by putting (site name /wp-admin)white screen of death error also might seem slightly different depending upon the browser. Here is an example in Google Chrome. It gives us a warning saying, “This page isn’t working and is unable to handle the request. The error shows (HTTP 500 error)

WordPress White Screen of Death

in other browsers like Mozilla Firefox, it is just a completely white screen with no errors.

How to Fix WordPress White Screen of Death

If you are seeing a white screen like on above picture, here are some common steps to resolve this issue:follow these steps one by one.

  • Disable or remove Plugins and Themes
  • Review (check) for Failed Auto-Update
  • Increasing Memory Limits throw (wp-config.php) using Cpanel
  • Check permission and ownership issues
  • Switch On Debugging ( define( ‘WP_DEBUG’, enable )
  • Resolve Syntax Errors

Disable or remove Plugins and Themes

The easiest and most common way to fix the WordPress white screen of death is to disable all your plugins. Several times, a site goes down due to a bad plugins update. If you are still eligible to access your admin, a smart way to do this is to browse to the “Plugins” and choose “Deactivate” from the bulk actions menu. With this, all of your plugins will disable. If this tip fixes the issue, you need to find the culprit. Then Start activating them one by one, reloading the website after all activation.if your website front-end goes down, you’ve found the misbehaving plugin. You can then reach out to the plugin developer for more help or post a support ticket in the WordPress representative for guidance.

If you can’t access your admin in WordPress, you can access your plugin using hosting Cpanel. follow these steps

  • Open hosting c panel.
  • Go to the file manager.
  • Open public html folder.
  • Open wp-content.
  • Now open the plugin file.
  • See the plugins which you need to delete.

The same goes for your WordPress themes. You can go to Cpanel then open the file manager then open WordPress in WordPress folder you will see the theme option you can delete the effected theme.on the other side if you have admin access then you can change your theme by opening the appearance option.

Review (check) for Failed Auto-Update

Several WordPress may run into an issue with updates, like the server timing out. And often than not, this fixes itself automatically; though, in some wild cases, this may start to a white screen of death.

The first thing you should do is go into your WordPress root directory and see if there’s a .maintenance file in there. Feel comfortable to delete that file and load up your website again. If the update was successful, but WordPress failed to remove this file automatically, everything will go back to normal.

If the update was not completed it may be done automatically for you, in which case things should go back to regular just the same. If each else fails, follow the advised WordPress manual update procedure which should resolve the issue once and for all.

Increasing Memory Limits throw (wp-config.php)

If still you are seeing an empty page or get a failure complaining about memory limits or weakened memory, you’ll require to assign more memory to the application. This can be done within the (wp-config.php) file on several installs, add the following code to the file

define(‘WP_MEMORY_LIMIT’, ‘128M’);

If still, this doesn’t seem to work, you have another few options. In a regular conditions, you can use your .htaccess file in Cpanel – in the WordPress root directory – to increase the memory limit, add the following line:

php_value memory_limit 128M

Check permission and ownership issues

We haven’t seen a white screen of death due to this, without permission and ownership effects can still cause difficulties. Who identifies, in some cases, it may point to a white screen of death! It is possible to fix this yourself, but except you know what you’re doing, we would advise against it. For WordPress, there are three simple rules:

  • files should be 664 or 644,
  • folders should be 775 or 755
  • and the wp-config.php file should be 660, 600, or 644

Switch On Debugging

If you are viewing the WordPress white screen of death or the WordPress admin option isn’t working (or if you’ve found the offender but want to dig deeper) you can enable debugging which expose all errors. The problem is that when a fatal error occurs, the script ends execution. If this issue occurs before any content is displayed, complete you’ll see in a white screen with certainly no text.

To enable debugging need to open the wp-config.php file of your WordPress install. Inside it, you should see the following line:

define( ‘WP_DEBUG’, false )

by seeing the upper line you need to replace false with true and reload your site.

Resolve Syntax Errors

Another essential reason for the white screen of death is if you were updating the code on your WordPress site and you unintentionally mistyped something or have the incorrect syntax. One defective character in the wrong place could take down your whole site. Yes, this is kind of scary! That’s one cause how? You should never edit code on your live production site.

Though, not to worry about this. You can always connect to your site via SFTP and return the change you made manually. If you are not aware, what changed caused it, this is why you should have then you should restore WordPress backups.

For iphone info click here

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button