If you are reading this article, you may be a big fan of WordPress. And it’s easy to know why. Content management systems (CMS) are powerful, but not without drawbacks. Platforms are usually robust, but given complexity and flexibility, errors or errors are inevitable. Therefore, it is very important to learn the basic knowledge of WordPress troubleshooting. Learning how to correct some of the most common mistakes in WordPress can solve any mistakes that don’t need help. That’s the kind of technology that can give you a lot of headaches. The
Before looking at the basics of WordPress troubleshooting, let’s take a look at the three most common errors on the platform. Let’s go! The three most common word press errors word press errors are displayed in various shapes and sizes, such as maintenance mode errors or connection timeout messages. But it will always be necessary to cover them all up, so we will focus on the three most common suspects we will face. 1.404 or page error not found 404 error is the most common and easy to correct error. This happens when someone navigates to a URL that cannot be found on your site for many reasons, such as broken links or incorrect addresses. It takes a few seconds to find and modify broken links, but you must first find the link and consider the security problems you and your visitors will encounter. The
For details on how to correct 404 errors, see the previous guide. 2. the WordPress bug dramatically named after the white screen of death (wsod) is also one of the most troublesome bugs. If the website suddenly starts to display a white screen, it will be attacked. Wsod is often caused by automatic upgrade problems, maintenance mode errors, or compatibility issues with plug-ins and topics. Due to all these potential causes, especially in the absence of cause clues, it is difficult to solve the problem. Like the 404 error, I have previously modified wsod. In WordPress, the method of modifying the white death screen provides a step-by-step guide to modifying the white death screen. The
3. unlike the internal server error wsod, the internal server error is easy to identify. If an error occurs, a large internal server error message is displayed, so no error occurs. Since there are many factors that may cause internal server errors, the actual problem occurs in the troubleshooting phase. Fortunately, we have written a complete guide to this topic before. I can thank you later! How to solve common word press errors it is important to read how to back up your site before using the word press troubleshooter to get your hands dirty. In fact, before modifying the WordPress installation, you must always back up your site in case of a worst-case scenario. The entire site may be lost. The
Incompatible plug-ins and themes are the main cause of errors. You should first stop when solving word press problems. However, there are other aspects that may affect the installation, including memory limitations and corrupt core files. Although you can use the file manager on the web host to perform the following steps, it is recommended to use FTP (File Transfer Protocol) clients such as FileZilla. After getting familiar with the speed, we will start to solve the problem! 1. before disabling the plug-in through FTP, open the FTP client and log in to the site using the credentials obtained from the web host during subscription. Then go to public_html>wp content. You can find multiple folders internally. The
Right click the plug-in folder, select Rename option, and then make changes as needed. Avoid confusing folders later
It is recommended to select the relevant name. This simple task will disable all plug-ins on the WordPress website. Then navigate to the web site and verify that the error that occurred persists. If yes, plug-in compatibility errors can be ignored as the cause of the problem. Conversely, if the error disappears, you must find out which plug-in caused the error. Rename the plug-in folder to its original name and open it. The folder for each plug-in can be found internally. To find the problem, rename each plug-in folder and verify that the error persists. If it disappears, you will know what plug-in caused it. At this point, you need to contact the developer to modify or find an alternative. The
2. if the problem cannot be solved by disabling the theme disabling plug-in through FTP, you must perform similar troubleshooting steps for the theme. Return to the FTP client, find the WP content: internal themes folder and enter WP content: instead of disabling themes in random order as in the male plug-in, the first stop here must be an active theme. Change the folder name to disable the folder, and then verify that the error persists. If so, repeat the process for each topic in the folder until the killer is found. As with plug-ins, you may want to contact the developer to make changes. However, considering the main role of plug-ins in site design, you must be looking for alternatives. The
If disabling the plug-in or theme doesn’t work, you almost have to throw a towel. However, we can activate the error log to pick up some valuable insights. 3. enable the error log. The error log allows you to save records whenever there is a problem in the site during WordPress installation. It is very useful from the perspective of troubleshooting. To enable error logging, go to public\u HTML from the FTP client, and then WP config. Navigate to the PHP file, right-click, and select edit functions. Use your preferred text editor to add the following three lines to the end of the file: The
Define (‘wp_debug’, true); Define (‘wp_debug_display’, false); Define (‘wp_debug_log’, true); Save the changes and reload the site to replicate the errors. The log is a new debug in WP content. It must appear in the log file to display WP content. You can use a text editor to access the file and use this information to inform Google of the dilemma, or find a local expert to solve the word press problem. The
Conclusion learning the basic knowledge of WordPress troubleshooting is not only useful in correcting errors, but also helpful to understand the internal operation of the platform. That is, you will know how to identify and fix problems even if there are errors (including those that you have no chance to deal with here). The next time you get a confusing word press error, remember the following: Back up your site before taking decisive action. Manually disable plug-ins and themes through FTP to eliminate compatibility errors. To view additional clues, enable the WordPress error log. If the above methods do not solve the problem, please consult a WordPress expert. You have performed WordPress troubleshooting before. How did you do it? Please tell me more in the comments section below!
