Is your site looking for ways to resolve conflicts? If you are interested, this post is very suitable, because finding the cause of the problem can save a lot of time. This guide provides two ways to activate WordPress debugging mode and find conflicts on the website. No matter how much you pay attention to it, some websites will always face all kinds of problems. Resolving these errors is not always easy, and it may take hours to find the cause of the conflict. Therefore, knowing how to solve and solve these problems is very important to avoid headaches. In this article, you will learn how to activate debugging mode in word press and solve the problem immediately.
Before entering it, let’s better understand what debugging mode is. What is the debug mode? Debugging patterns are techniques that developers use to identify potential threats and warnings from PHP or other programming languages. As we all know, word press is built with PHP, JavaScript, HTML and CSS, so code errors may lead to some errors. For example, a site may be damaged if: PHP version update add custom code add new theme \/ plug-in install theme \/ plug-in update text imprint update usually plug-ins conflict due to update or incompatibility. There are many problems, from harmless conflicts to problems on the checkout page, or the emergence of a death white screen in bad luck. By default, word press doesn’t have built-in monitoring for these conflicts, so it’s hard to know what happened. The good news is that you can do something to check for errors and fix them before it’s too late. This can solve the problem more accurately and faster.
If debug mode is enabled, WordPress will display all errors in the administration area directly below the top navigation bar. This allows you to quickly follow alerts and modify what you need. Not all errors need urgent attention, but as long as there are errors and they are corrected immediately, it can help you provide a good user experience without deteriorating the situation. Now, let’s look at various ways to activate debug mode. To enable WordPress debugging mode, you can enable WordPress debugging mode in the following two ways: Manual use of plug-ins this section lists two methods, and you can choose the best method according to your needs.
1) If you have the coding technology of manually activating debugging mode and are familiar with the editing of core files, this method is very suitable. To enable debug mode, WP config. The code snippet must be added to the PHP file. You can use an FTP client or a dedicated file manager plug-in, such as FileZilla. This demo uses the file manager plug-in. Note: changes are simple, but it is recommended that you always create a site backup before you start. 1.1) the first task of installing and activating the file manager is to install and activate the file manager plug-in in the word press installation. Plug ins > navigate to new plug-ins, search for and install plug-ins.
Male 1.2) after activating the plug-in configuration, open the plug-in settings in WP file manager. You can view all directories and files hosted by the server. 
wp-config. It is recommended that you a copy of the PHP file to your local computer before modifying it. If there is a problem, you can easily delete the modified version and upload the parent file. Add other precautions in this way. After ing the file, WP config in the file manager. Right click the PHP file and modify it using the code editor options
.
Male 1.3) after opening snipt, the editor will be displayed. You can add or remove code from the file. Male scroll down \/ * that’s all, the line that stops editing will be displayed. Happiness publishing. * * \/. Copy and paste the following code directly in front of the line: Definition (\
That’s not all. The problem with this snipet is that all conflicts (if any) on the website are displayed on the front and back ends. That is, if the site is active, visitors can view warnings, causing confusion. Is there any way to hide? Yes, yes! In addition, it may be convenient to keep a log of all problems. 1.4) to hide the snipet warning of the front-end hidden warning and keep the log, use the snipt below to paste it under the debugging code just added. 
\/\/ debug. Set the log to \/ WP content \/ debug. Define save in log (\
When you’re done, don’t forget to save your settings. WordPress now manually activates debug mode. From now on, you can continue to view notifications, but site visitors cannot view notifications on the front end. If you don’t like this method, there are other alternatives. 2) If you don’t want to edit the debug mode to activate the core file with the plug-in, you can activate the debug mode with the plug-in. This section describes how to do this step by step. WP debugging is a special plug-in that enables debugging mode in all word press installations. This section will learn how to follow the steps.
2.1) before installing and activating WP debugging, the WP debugging plug-in must be installed and activated on the website. The plug-in is located in the repository, so navigate to plug ins > New in the management panel to browse and install the plug-in. Male 2.2) after installing and activating the plug-in configuration plug-in, the configuration will be displayed below the tool section. The plug-in will the following code WP config. Automatically added to PHP files. Definition (\
In this way, errors will be displayed on the front end. Therefore, if you want to hide the warning, you’d better select the option \
If debug mode for checking error messages is enabled, WordPress saves a log of all problems on the server. You can use the FTP client or a dedicated plug-in to find logs in the file manager. This section will learn how to check error messages correctly
