{"id":58373,"date":"2020-12-01T14:19:59","date_gmt":"2020-12-01T20:19:59","guid":{"rendered":"https:\/\/blog.cpanel.com\/?p=58373"},"modified":"2020-12-01T14:19:59","modified_gmt":"2020-12-01T20:19:59","slug":"wordpress-debugging-with-cpanel-and-wp-toolkit","status":"publish","type":"post","link":"https:\/\/devel.www.cpanel.net\/blog\/tips-and-tricks\/wordpress-debugging-with-cpanel-and-wp-toolkit\/","title":{"rendered":"WordPress\u00ae Debugging with cPanel and WP Toolkit"},"content":{"rendered":"\n
WordPress\u2019s greatest strength is that it just works. There is little for the average user to worry about beyond installing plugins, tweaking themes, and applying updates. However, as with any complicated software, bugs in WordPress\u2019s code can cause unexpected behavior, especially during the development of plugins, themes, and custom functions. <\/p>\n\n\n\n
WordPress has built-in debugging tools, but using them can be awkward and time-consuming. They are turned off by default and can\u2019t be configured in the web interface. cPanel\u2019s WP Toolkit <\/em>makes debugging faster and more convenient by providing an intuitive interface to configure logging and diagnose errors.<\/p>\n\n\n\n In this article, we\u2019ll show you how to use the WP Toolkit<\/em> to:<\/p>\n\n\n\n WordPress\u2019s debugging mode tells the software to log error messages and warnings produced by the underlying PHP code. Error logs help developers to figure out the cause of unexpected behavior. Debugging is usually turned off because it consumes server resources and creates a potential security vulnerability. The logs reveal information about WordPress\u2019s internal state that it\u2019s better to keep secret. To turn on debugging mode, select a site in the WP Toolkit<\/em> interface and click the Debugging <\/em>switch in the Tools <\/em>section.<\/p>\n\n\n\nActivate and Configure WordPress Debugging Modes<\/strong><\/h2>\n\n\n\n