WP Toolkit provides controls for WordPress debugging. Debugging can help identify PHP errors, warnings, and other problems during development or troubleshooting.
- Open WP Toolkit: cPanel → Domains → WP Toolkit or Plesk → WordPress.
- Find the affected website.
- Open Debugging.
- Enable only the debugging options you need.
- Save the settings and reproduce the problem.
Use debugging carefully on production sites
Detailed errors can reveal file paths, plugin names, or other technical information. On a public production website, logging errors is generally safer than displaying them to visitors.
When troubleshooting is complete, return to WP Toolkit and disable debugging options that are no longer required.
Debugging is useful when a page is blank, a plugin or theme throws errors, custom code fails, or an application developer needs diagnostic information.
A hidden error is not a protected log. The default wp-content/debug.log may be downloadable. Prefer staging; use a verified private log destination or enforced access protection, then disable debugging and remove unnecessary logs. See Using WordPress Debug Logging Without Exposing Errors to Visitors in Troubleshooting.
Documentation for this guidance: developer.wordpress.org — debug wordpress.
Panel navigation and availability: cPanel WP Toolkit feature guidance; Plesk WP Toolkit guide.
