EDITS.WS

Tag: deactivate plugins

  • How to Fix the WordPress White Screen of Death (Step by Step)

    The WordPress white screen of death is one of the most common WordPress errors. It is also a frustrating error because there is no message, and you are locked out of WordPress.

    Another problem with the white screen of death error is that sometimes, it only affects a certain part of your website. For example, you may only see the white screen of death inside the WordPress admin area, while everything else works fine. In other cases, you might only see it on a specific post.

    In this article, we will show you how to fix the WordPress white screen of death by looking at different solutions.

    How to Fix the WordPress White Screen of Death (Step by Step)

    Note: Before you make any changes to your site, make sure you have a backup of your WordPress site. If you don’t have access to the admin area, then see our guide on how to manually create a WordPress database backup.

    Why Do You See the White Screen of Death in WordPress?

    The majority of the time, when you see a white screen of death when trying to visit your WordPress website, it means that a script on your website exhausted the memory limit.

    The unresponsive script either gets killed by your WordPress hosting server or simply times out. This is why no actual error message is generated, and you just see a plain white screen.

    WordPress showing white screen instead of website

    However, sometimes, you may see an error message.

    For example, you might see a critical error message instead of a plain white screen.

    Critical error in WordPress

    Whether you are seeing a blank screen or the message ‘There has been a critical error on your website’, it’s the same error.

    This error can also happen due to a poorly coded theme or plugin installed on your site. Sometimes, it can happen if there is an issue with your web hosting server.

    Since the white screen error can be caused by any number of things, it requires methodical troubleshooting to fix it. Here are the steps you should try:

    Video Tutorial

    If you’d prefer written instructions, then just keep reading.

    1. Check Whether the Problem Happens on Your Other Sites

    If you have other WordPress sites installed on the same hosting account, then you want to start by checking if the problem is happening on other sites as well.

    If it is, then that’s a strong indicator that something is wrong with your WordPress hosting service. This could be a temporary issue affecting their service, and you need to reach out to their support for more help.

    On the other hand, if the issue is only happening with one website or a specific part of that site, then you know that the problem is with that particular website.

    2. Fix the White Screen Error With WordPress Recovery Mode

    If the white screen of death error is caused by a WordPress plugin or theme, then WordPress may be able to catch it.

    The new fatal error protection feature introduced in WordPress 5.2 can sometimes catch the error, so you may not even see a white screen. Instead, you will see a message that the site is having technical difficulties.

    This Site Is Experiencing Technical Difficulties Error Message

    WordPress will also send an email about the problem to your admin email address.

    The email will have the subject ‘Your Site is Experiencing a Technical Issue’.

    Technical Difficulties Email With Link to Recovery Mode

    This email message will point out the plugin or theme causing the error, and it will also contain a special link.

    This link will allow you to log in to the WordPress recovery mode and deactivate the faulty plugin.

    WordPress recovery mode dashboard

    However, if you are seeing the plain white screen of death with no email or recovery mode option, then you need to manually fix the error.

    3. Increase the Memory Limit

    Usually, this error happens because a script has exhausted your web server’s memory and quit in the middle.

    To fix this, you need to increase the PHP memory available to WordPress. This will allow the script to use more memory to finish the job it was supposed to do.

    You will need to edit the wp-config.php file on your WordPress site or use a code snippet plugin like WPCode

    You can follow the instructions in our tutorial on how to increase PHP memory in WordPress.

    4. Fix the White Screen Error by Disabling All Plugins

    If increasing the memory limit did not help, or if you have a high memory limit, like 256M or 512M, then you need to start troubleshooting.

    In our experience of troubleshooting this issue, we have always found that the issue is either with a specific plugin or a theme. Let’s go ahead and disable all the plugins.

    If you can still access the WordPress admin area, then you can simply go to the Plugins » Installed Plugins page. Select all the installed plugins and then select ‘Deactivate’ under the ‘Bulk actions’ dropdown.

    Deactivate all WordPress plugins

    However, if you don’t have access to the WordPress admin area, then you will need to deactivate all plugins via FTP.

    First, connect to your WordPress site using an FTP client. Once connected, go to the wp-content folder, where you will see the plugins folder.

    Now, you need to right-click on the plugins folder and then select ‘Rename’. You can rename the plugins folder to ‘plugins-deactivated’.

    Using FTP to Rename the Plugins Folder

    WordPress looks for a folder named plugins to load all plugins. When it cannot find the folder, it simply deactivates all plugins.

    If this fixes the issue, then enable one plugin at a time to get to the bottom of the issue. Once you find the plugin causing the issue, you can replace it with an alternative or report the issue to plugin authors.

    5. Activate the Default Theme

    If the plugin troubleshooting doesn’t fix the issue, then you should try replacing your current theme with a default theme.

    First, connect to your website using an FTP client and go to the /wp-content/themes/ folder. It contains all installed themes on your website.

    Right-click to select your current WordPress theme and download it to your computer as a backup.

    Using FTP to Download the Current Theme as a Backup

    Next, you need to delete your current theme from your website.

    Simply right-click on your theme folder and select ‘Delete’. Your FTP client will now delete the theme from your website.

    Using FTP to Delete the Current Theme

    Now, if you have a default WordPress theme like (Twenty Twenty-Two or Twenty Twenty-Three) installed on your website, then WordPress will automatically start using it as the default theme.

    However, if you don’t have a default theme installed, then you need to manually install it using FTP.

    If this fixes the issue, then you should look at your theme’s functions.php file. If there are extra spaces at the bottom of the file, then you need to remove those, and sometimes that fixes the issue.

    If you are using a poorly coded function in your theme’s functions.php file, then it can cause the white screen of death error as well.

    Consider downloading a fresh copy of your theme from its source and then installing it manually using FTP.

    6. Enable Debug Mode to Catch Errors in WordPress

    If nothing has helped so far, then the next step is to turn on debugging in WordPress. This will allow you to see what type of errors are being outputted.

    Simply add the following code to your wp-config.php file:

    define( 'WP_DEBUG', true);
    define( 'WP_DEBUG_LOG', true );
    

    Once you add this, the blank screen will now have errors, warnings, and notices. These may be able to help you determine the root cause.

    If you don’t see any errors, then you may still want to check the debug log.

    Simply visit the wp-content folder on your website using an FTP client. There, you will find a new debug.log file containing a log of all errors, notices, and warnings.

    Debug log

    7. Clear the WordPress Cache

    Sometimes, you may have access to the backend, but the front end of the site has the white screen of death.

    This can happen because of a caching plugin. In that case, you simply need to empty your WordPress cache.

    You can see our guide on how to clear the cache in WordPress for detailed instructions.

    8. Fix the White Screen Error for Longer Articles

    If you have a white screen of death only on a very long post or page, then this method might work.

    This trick basically increases PHP’s text processing capability by increasing the recursion and backtrack limit. You can 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);
    

    We understand that this is a very frustrating error, and we hope that one of the tricks above has fixed the issue for you.

    You may also want to see our WordPress troubleshooting guide, which teaches the steps you should take to catch and fix WordPress problems by yourself, or our expert pick of the best WordPress managed hosting providers.

    If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

    The post How to Fix the WordPress White Screen of Death (Step by Step) first appeared on WPBeginner.

  • How to Fix the 500 Internal Server Error in WordPress

    Are you seeing a 500 internal server error in WordPress?

    The internal server error is one of the most common WordPress errors. Since the error doesn’t give any other information, many beginners find it quite frustrating.

    In this article, we will show you how to easily fix the 500 internal server error in WordPress.

    Fixing the internal server error in WordPress

    Here is a quick overview of the topics we’ll cover in this article.

    What is The 500 Internal Server Error?

    The 500 internal server error is a common web server error. It is not specific to WordPress websites and can happen with any website.

    The 500 in the error message is technically an HTTP error code. Looking up this code will only show its standard description.

    500 Internal Server Error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

    This is a generic catch-all error message which means that the server was unable to assign a better more helpful error message when it encountered the issue.

    The error page looks different depending on which web server software (Nginx or Apache) your website is using and which browser you are using.

    Here is how the Apache error page may look.

    Internal server error page on Apache

    It may look different if you are using Nginx and Google Chrome.

    It will also look different if Google chrome is unable to find an error page to display:

    Google Chrome http 500 error

    For beginners, this can be incredibly frustrating. There is no clue or message that would point them in the right direction to quickly fix it.

    Asking how to fix an internal server error is like asking your doctor how to fix the pain you’re experiencing without telling them where the pain is.

    However, if we know the common causes that trigger this error, then we can try fixing them one by one to resolve the error without breaking anything.

    What Causes The Internal Server Error in WordPress?

    Internal server error in WordPress is often caused by a corrupt .htaccess file, poorly coded plugins, or your active WordPress theme.

    Other possible causes of the internal server error in WordPress that we know of are: PHP memory limit or corrupt core WordPress files.

    In some conditions, the internal server error may only show up when you are trying to access the WordPress admin area while the rest of the site works fine.

    That being said, now let’s take a look at how to go about troubleshooting the internal server error in WordPress.

    Video Tutorial

    If you prefer written instructions, then continue reading.

    Fixing The 500 Internal Server Error in WordPress

    Before you begin troubleshooting, make sure that you have a complete WordPress backup of your website on hand.

    If you have access to the WordPress admin area, then you can a WordPress backup plugin to create a complete backup of your website. We recommend using Duplicator to handle this.

    On the other hand, if you don’t have access to the WordPress admin area, then you can manually create a WordPress backup using phpMyAdmin and an FTP client.

    After that, you can follow the following steps to troubleshoot and fix the internal server error on your website.

    Clear WordPress and Browser Cache

    Browsers and your WordPress caching plugins can sometimes mistakenly store a cached copy of an error page.

    The easiest way to fix this is by first clearing your browser cache.

    Clear cache

    After that, if you have access to the WordPress admin area of your website, then you can empty the WordPress cache by visiting your caching plugin’s settings page.

    For details, see our tutorial on how to clear WordPress cache.

    Checking for Corrupt .htaccess File

    The .htaccess file is a server configuration file that is also used by WordPress to set up redirects.

    One of the most common causes of the internal server error is the corrupt .htaccess file.

    The easiest way to fix this is by simply visiting the Settings » Permalinks page in the WordPress admin area and then clicking on the ‘Save Changes’ button without making any changes at all.

    Update permalinks to regenerate .htaccess file

    WordPress will now try to update your .htaccess file or generate a new one for you. You can now visit your website to see if this has resolved the internal server error.

    If you can still see the error, then you need to make sure that WordPress was able to generate or write to the .htaccess file.

    Sometimes, due to file and directory permissions, WordPress may not be able to create or write to your .htaccess file.

    You can now try to manually replace the .htaccess file. First, you need to login to your website using FTP or the File Manager app under your hosting account control panel.

    Next, you need to rename your main .htaccess file to something like .htaccess_old. This lets you keep the file as a backup, but WordPress won’t recognize it.

    To rename the .htaccess file, you will need to login to your site using FTP or File Manager app in your hosting account’s cPanel dashboard.

    Once you are connected, the .htaccess file will be located in the same directory where you will see folders like wp-content, wp-admin, and wp-includes.

    Simply, right-click on the .htaccess file and rename it to .htaccess_old.

    Rename .htaccess file

    Next, you need to create a new .htaccess file.

    Inside your site’s root folder, right-click and then select ‘Create new file’ option in your FTP client or File Manager app.

    Create new htaccess file

    Name this new file .htaccess and click OK to save it.

    Now, this .htaccess file is currently empty and you need to add default WordPress rewrite rules to it.

    Simply right-click on the file and then select View/Edit in your FTP client or File Manager app.

    Editing .htaccess file in WordPress

    The empty file will open in a plain text editor like Notepad or TextEdit. Now, you need to copy and paste the following code inside it.

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress
    

    This code is the default rule set used by WordPress. Don’t forget to save your changes and upload the file back to the server.

    You can now visit your website to see if this has resolved the internal server error.

    If it did, then give yourself a pat on the back because you fixed the internal server error.

    Important: Before you move on with other things, make sure that you go to Settings » Permalinks page in the WordPress admin area and click the save button without making any changes. This will regenerate the .htaccess file for you with proper rewrite rules to ensure that your post pages do not return a 404 error.

    If checking for the corrupt .htaccess file solution did not work for you, then you need to continue reading this article.

    Increasing the PHP Memory Limit

    Sometimes the internal server error can happen if a script is consuming all the PHP memory limit.

    The easiest way to increase the PHP memory limit is by editing the wp-config.php file. Be careful when you do this if you’re a beginner. You want to follow these instructions carefully because even small mistakes in WordPress core files can break your site.

    To begin, simply connect to your WordPress website using an FTP client or the File Manager app under your hosting account control panel.

    You’ll find wp-config.php file inside the main folder of your website. Right-click on it and select ‘Download.’ This will ensure that you have a backup of the file in case something goes wrong.

    When you’ve saved that, you can right-click on it and select ‘View/Edit.’

    Edit wp-config file

    Inside the wp-config.php file, you need to add the following code just above the line that reads ‘That’s all, stop editing! Happy publishing’.

    define( 'WP_MEMORY_LIMIT', '256M' );
    

    For more details, see our tutorial on how to increase PHP memory limit in WordPress.

    If you are seeing the internal server error only when you try to log in to your WordPress admin or upload an image in your wp-admin, then you should increase the memory limit by following these steps:

    1. Create a blank text file on your computer and name it php.ini
    2. Paste this code in there: memory=256MB
    3. Save the file
    4. Upload it into your /wp-admin/ folder using FTP

    If increasing the memory limit fixed the problem for you, then you have only fixed the problem temporarily. You still need to find the cause that is exhausting your memory limit.

    This could be a poorly coded plugin or even a theme function. We strongly recommend that you ask your WordPress web hosting company to look into the server logs to help you find the exact diagnostics.

    If increasing the PHP memory limit did not fix the issue for you, then you are in for some more troubleshooting.

    Deactivate All WordPress Plugins

    If none of the above solutions worked for you, then this error is most likely being caused by a specific plugin installed on your website.

    It is also possible that it is a combination of plugins that are not playing nice with each other.

    If you can access the WordPress admin area of your website, then you can simply go to the plugins page and deactivate all WordPress plugins.

    Deactivate all plugins

    However, if you are unable to access the WordPress admin area, then you can deactivate all WordPress plugins using FTP.

    Simply connect to your WordPress website using an FTP client or the file manager app under your hosting account control panel.

    Once connected, navigated to the /wp-content/ folder and rename the plugins folder to plugins.deactivated.

    Plugins deactivated via FTP

    WordPress looks for plugins in the plugins folder. If the plugins folder is not found, then it will automatically deactivate all plugins.

    You can now try visiting your website to see if this resolved the internal server error on your website.

    To restore all your plugins, you can simply rename the plugins.deactivated folder back to plugins.

    Your plugins will now be restored but they will still be deactivated.

    You can now activate plugins one by one and visit your website to figure out which plugin is causing the internal server error.

    For more details, see our guide on how to deactivate all WordPress plugins without WP-Admin.

    If deactivating all plugins didn’t fix the internal server error on your website, then continue reading.

    Switch to a Default WordPress Theme

    One possible cause of the internal server error could be some code in your WordPress theme.

    To find out if this is the case, you need to switch your theme to a default WordPress theme.

    If you have access to the WordPress admin area, then simply go to the Appearance » Themes page. If you have a default theme already installed then you can simply click on the Activate button to switch theme.

    Activate a default theme

    If you don’t have a default theme installed, then you can click on the Add New button at the top and install a default theme (Twenty Twenty-Three, Twenty Twenty-Two, etc).

    Now in case you don’t have access to the WordPress admin area, you can still switch to a default theme.

    Simply, connect to your WordPress website using an FTP client and navigate to the /wp-content/ folder.

    Right-click to select the themes folder and download it to your computer as a backup.

    Download theme folder

    Next, you need to delete the themes folder from your website. Once it is deleted, go ahead and create a new themes folder.

    Your new themes folder will be completely empty which means you don’t have any WordPress themes installed at the moment.

    Next, you need to visit the WordPress themes directory and download a default WordPress theme to your computer.

    Download a default theme

    Your browser will then download the theme as a zip file to your computer.

    Locate the file on your computer and then unzip it. Windows users can unzip file by right-clicking on it and then selecting Extract All. Mac users can double-click on the zip file to extract it.

    Extract theme files

    You’ll now see a folder containing your WordPress theme.

    Switch back to your FTP client or File Manager up and upload this folder to the empty themes folder.

    Upload theme files

    Once uploaded, WordPress will automatically start using the default theme.

    You can now visit your website to see if this resolved the internal server error.

    If this didn’t work, then you can reupload your WordPress themes from the backup or switch back to the theme you were using.

    Don’t worry there are still a few more things you can do to fix the error.

    Re-uploading Core Files

    If the plugin and theme options didn’t fix the internal server error, then it is worth re-uploading the /wp-admin/ and /wp-includes/ folders from a fresh WordPress install.

    This will NOT remove any of your information, but it may solve the problem in case any file was corrupted.

    First, you will need to visit the WordPress.org website and click on the Download button.

    Download WordPress

    This will download the WordPress zip file to your computer.

    Go ahead and extract the zip file. Inside it, you will find a wordpress folder.

    WordPress folder extracted

    Next you need to connect to your WordPress website using an FTP client.

    Once connected go to the root folder of your website. It is the folder that has wp-admin, wp-includes, wp-content folders inside it.

    In the left column open the WordPress folder on your computer.

    Now you need to select all files inside the wordpresss folder and upload them to your website.

    Upload core WordPress files

    Your FTP client will now transfer those folders to your server.

    It will ask you whether you would like to overwrite the files. Select ‘Overwrite’ and then select ‘Always use this action’.

    Overwrite WordPress core files

    Your FTP client will now replace your older WordPress files with new, fresh copies.

    If your WordPress files were corrupted, then this step will fix the internal server error for you.

    Enable Debug Logs in WordPress

    WordPress comes with a built-in system to keep logs for debugging.

    You can turn it on by using the WP Debugging plugin. For more details, see our guide on how to install a WordPress plugin.

    Once activated, the plugin will turn on debugging logs on your WordPress website.

    If you don’t have access to the admin area of your WordPress website, then you can turn on debugging by adding the following code to your wp-config.php file.

    define( 'WP_DEBUG', true);
    define( 'WP_DEBUG_LOG', true); 
    

    Once you have turned on debug logs, you can view these logs by using an FTP client and navigating to the /wp-content/ folder.

    Debug log

    You can open the debug log file in a text editor and it will show you a list of errors and warnings that occur on your website.

    Some of these errors and warnings can be harmless incidents that may not need fixing. However, if you are seeing an internal server error on your website then these may point you in the right direction.

    Ask your Hosting Provider

    If all methods fail to fix the internal server error on your website, then it is time to get some more help. Contact your web hosting support team and they will be able to check the server logs and locate the root cause of the error.

    If you want to continue troubleshooting on your own, then see our ultimate WordPress troubleshooting guide for beginners.

    We hope this article helped you fix the internal server error in WordPress. You may also want to see our complete list of the most common WordPress errors, and our guide on how to choose the best web hosting provider.

    If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

    The post How to Fix the 500 Internal Server Error in WordPress first appeared on WPBeginner.