Learn more about modifying the memory limit or maximum running time of the server every day to adjust the hosting.
1. To modify the browser cache and cookie to erase wsod, the first thing to do is to check whether there is a problem in the browser. To do this, you must clear the browser’s cache and cookies. Different browsers have different ways to clear cached data and cookies. For example, in chrome, you must click the three dot icons in the upper right corner and go to other tools > delete Internet usage record. A new page with search data pop-up appears. You can select the data to delete here. Now check the cached images, files, and cookies whose time range is set to full time, and then click clear data. This will clear all browser caches and cookies.
If there is a problem with the browser, the problem will be solved and you can visit the website. But if it doesn’t work, the problem is on the website. In this case, please continue to the next step. 2. Clear the WordPress cache. Another solution to modify white screen of death is to clear the WordPress cache. To do this, you must have access to the WP Management Dashboard. Note: in some cases, white screen of death will also affect the administrator page, so the site is locked and inaccessible. In this case, this solution does not work, so you can continue to use the next solution.
For users who can access the WP Management Dashboard, you can erase the WordPress cache. By default, WordPress does not provide a way to delete cached data, so plug-ins must be used. This tutorial will use WP rocket. First, install and activate the plug-in. Then navigate to the manager dashboard, navigate to Settings > WP rocket, and click the clear cache button in the dashboard section. That’s all! All cached data will now be deleted. The word press cache data has now been deleted. Please check whether the problem persists. If yes, go to the next step.
3. Viewing the steps before moving to wsod can help solve and repair the word press white screen of death problem. By copying what you did before wsod appeared, you can find the right problem, or at least get a hint of the cause of the error in the beginning. What you need to understand is to look back and remember what you or your team members did before the white screen appeared. Unfortunately, there is not much help available at this stage, and finding errors is entirely up to you. But there are a few things I hope you can observe while reflecting on your behavior.
Most importantly, remember what you or your team members are doing before the death white screen appears. Are new plug-ins or themes installed, or have existing plug-ins been modified? Have WordPress, plug-ins, or themes been updated? Have you changed the database or core file? Is there a new third-party integration with WordPress? During this time, did anyone on the team visit WordPress? What are they doing? This is just a reference to a few questions to help remember all the behaviors before encountering the white screen of death. This can better determine the cause of the problem and apply potential modifications to restore the site.
However, whenever a white screen appears, no one may be working in word press. In this case, the undo step may not be a viable solution and you must go to modify. 4. One of the main messages of starting recovery mode WordPress 5.2 is the fatal error proofing function
So, compared to a white screen without information, \
If the problem remains unresolved or WordPress does not receive an email, please continue to the next step. 5. Conflicts with all disabled plug-ins are one of the most common causes of WordPress white death screen. In particular, new plug-ins have recently been installed or existing plug-ins have been updated. To determine whether one of the plug-ins causes problems, you must disable all plug-ins. There are several ways to disable all plug-ins in batch. If you have access to the manager dashboard, navigate to plug ins > installed plug ins, select all plug-ins, and set batch tasks to disabled. Then click the Apply button to disable all plug-ins. On the contrary, if you cannot access the administrator dashboard, you must access the site directory through an FTP client (such as cPanel or FileZilla). Under the WP content folder of the site directory, there is another folder named plugins. To disable all plug-ins, replace the folder name with a different name than the plug-in. After disabling all plug-ins, go to the website and confirm whether the white screen disappears. Then, before the white screen appears again, please activate each plug-in one by one to find the plug-in that triggers the death white screen. For more information on how to disable all plug-ins at once, see the guide for this step. After identifying the defective plug-in, you can roll back the plug-in to an earlier version or contact customer support. Alternatively, you can find other similar tools to achieve the same functionality. However, if the plug-in is disabled but WordPress white screen of death is not modified, you must continue to find the reason. 6. If the change plug-in of the default theme is disabled, but wsod cannot solve it, the next thing to check is the theme. To determine if there is a problem with the theme, replace it with the default theme. When you solve the problem in this way, you will find that the theme is after white screen of death. To change the theme to the default theme, you must access the site directory through the host cPanel or FTP client. When the WP content folder is found in the directory, a folder named theme is displayed. This folder contains all ed topics. Find the currently active theme in the theme folder. If you haven’t already done so, it’s recommended to do so. Then select and delete the activity theme. This changes the site to the default WordPress Theme (for example, Tweety Tweety one). If there is no default theme or the default theme has been deleted previously, you must manually upload the default theme file to the website directory. After the problem is solved, make sure to switch to the default website. If the white screen of death is not displayed, the subject is the cause of the problem. In this case, if the topic is recently updated, you can roll back to the previous version. In addition, function. Make sure there are programming errors or spaces at the end of the PHP file. This is likely to solve the problem. Otherwise, please contact the theme developer for technical support. Even if you switch to the default theme, if the white screen does not disappear, the problem lies elsewhere and needs to be further studied. seven
In addition to WordPress integration verification plug-ins and themes, other third-party tools can be integrated with WordPress sites. For example, SSL certificate or CDN (content delivery network) such as Amazon cloud front. It is important to know that white screen of death may occur due to conflicts between third-party integrations. For example, a conflict between Amazon CDN and the SSL certificate provided by the host may lead to site downtime. To determine if the problem is in the WordPress integration, remember the activities you performed before displaying the white screen. You need to ask yourself a few questions: Is your site connected to a new service? Have you modified the settings of the configured service? wait. If these actions are performed, these changes must be returned to resolve the problem and successfully identify the root cause. If some of these services fail, you may need to find alternatives to these services or consult your service provider for solutions. However, if the integration works and WordPress cannot modify the white screen of death, go to the next step. 8. If enabling debugging mode has no effect so far, you may need to enable debugging mode. This helps you find potential PHP errors that may cause wsod. Debug mode will debug all errors that occur on the site. Log to the log file. Based on this information, you can determine the cause of the death of the white screen and take corrective measures to solve the problem. To enable debug mode, you must access the site directory. You can use cPanel or FileZilla or other FTP clients to do this. In the site directory, WP config. Browse the PHP file and open it in a text editor. Male then search for the next line. Define (\
Navigate to the T directory and replace the current file with the new file you just copied. Now, please go back to the site and make sure the problem is solved. Alternatively, if the site’s most recent backup is not currently changed, you can restore it. I hope the problem can be solved. If you still cannot modify WordPress white screen of death, go to the next solution. 10. If the memory limit or maximum running time adjustment of the server has no effect so far, the last thing you can try is to adjust the memory limit or maximum running time of the server. Sometimes, because there are not enough resources to process requests to enter the server, the site will crash and a white screen will appear. To solve this problem, you can manually increase the memory limit and maximum running time of the server. The problem may be in one of the two, and sometimes in both. First, increase the memory limit. If it still doesn’t work, increase the maximum running time. To increase the memory limit of the server, WP config. php, . Htaccess or PHP. Add a line of code to one of the INI files. WP config needs to edit these files. Let’s start with PHP and check whether the problem has been solved. Otherwise, proceed to the next step. Htaccess file, etc. wp-config. Add the following line to the PHP file: Definition (\
You should have understood that this will trigger the screen. Therefore, be very careful when changing the site. Wsod is difficult to solve, so it is avoided at any cost. Here are some precautions to avoid the fear of white screen of death: Even with plug-in updates, track your and your team members’ activities in WordPress. If there is a problem, help you review the steps when solving the problem. Back up regularly and store it in a safe location that can be accessed later. This is especially important before editing core files or making major changes to the site. If you don’t know how to create a backup, check the guidelines for this step. Always test your code in an offline environment before publishing it to WordPress. Small mistakes can be big trouble, semicolon \
