Enable Debugging<\/strong><\/p>\n\n\n\n To get started in your WordPress debugging quest, you\u2019ll first need to know how to start the damn debugger, right? Fortunately, getting the debugger going is easy enough. WordPress was developed with the end user in mind, and all of its debugging tools are easy to access and simple to comprehend. And, if you have some prior experience with debuggers, you\u2019ll be pleasantly surprised at how easy it is to understand any WordPress log dumps compared to other platforms. First, log onto the WordPress cPanel or connect using SSH. Open your \u201cwp-config.php\u201d file and edit it using your preferred text editor. Add the line: \u201cdefine(\u2018WP_DEBUG\u2019, true);\u201d to the config file. Now, you\u2019ll get notifications for any warnings, errors, and notices that might occur once you save the config file and exit the text editor. When you finish your debugging, you\u2019ll need to be sure to disable debugging to shut off the notification stream. To disable the debugger, open the config file again and change the line to \u201cdefine(\u2018WP_DEBUG\u2019, false);\u201d.<\/p>\n\n\n\n Just getting your WordPress debugger going is often enough to find the answer to your issue, but sometimes you\u2019ll need to dig deeper to find the underlying issue. That\u2019s why WordPress included some other useful debugging commands that you can try when the standard debugger isn\u2019t enough. Add these commands to the \u201cwp-config.php\u201d file (the same way you added the debugger command earlier) when you want to give your error detection a bit more oomph. To push all error data to a log file for parsing and issue identification, enable WP_DEBUG_LOG by changing its config line to \u201cdefine(\u2018WP_DEBUG_LOG\u2019, true);\u201d, and wait for the logs to start streaming in. Be sure to change \u201ctrue\u201d to \u201cfalse\u201d when you\u2019re done to avoid filling up your logs. If you\u2019re concerned about scripting issues, you can also use a config-file entry to set up your investigation. Enable SCRIPT_DEBUG in the config file by changing the line to \u201cdefine(\u2018SCRIPT_DEBUG\u2019, true);\u201d \u2014this will force WordPress to use core JavaScript and CSS development cores rather than the usual compressed ones.
<\/p>\n\n\n\n![\"\"](\"https:\/\/careerkarma.com\/blog\/wp-content\/uploads\/2019\/05\/glenn-carstens-peters-203007-unsplash-1.jpg\")
Know Your WordPress Debug Optional Commands<\/strong><\/h2>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n