How to Enable WordPress Debug Mode Safely

When your WordPress site breaks — a white screen, a plugin error, or an unexpected crash — WordPress typically swallows the actual PHP error and shows you nothing. Debug mode forces WordPress to surface those hidden errors so you can fix them. Here is how to enable it safely on your Hostinap Shared or Business Hosting account without exposing error details to your site visitors.

Step 1: Open wp-config.php

1. Log in to cPanel > File Manager.
2. Navigate to your public_html directory.
3. Find wp-config.php, right-click it, and choose Edit. Click Edit in the confirmation dialog.

Step 2: Add the Debug Constants

Locate the line that reads:

define( 'WP_DEBUG', false );

Replace it (or add these lines directly above the /* That's all, stop editing! */ comment) with:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

• WP_DEBUG true — Turns on error detection.
• WP_DEBUG_LOG true — Saves all errors to a log file (wp-content/debug.log) instead of displaying them on screen.
• WP_DEBUG_DISPLAY false — Prevents errors from being shown to your website visitors. Always set this to false on a live site.

Click Save Changes.

Step 3: Reproduce the Error and Check the Log

1. Visit your website and reproduce whatever action was causing the error (load the page, submit the form, etc.).
2. Go back to cPanel File Manager and navigate to public_html/wp-content/.
3. Open the debug.log file. Scroll to the bottom to see the most recent errors.

You will see entries like:

[22-Aug-2026 02:30:00 UTC] PHP Fatal error: Call to undefined function
my_plugin_function() in /home/user/public_html/wp-content/plugins/my-plugin/my-plugin.php on line 47

This tells you the exact plugin file and line number that is broken.

Common Error Types and What They Mean

• PHP Fatal error: Something critical broke — a function doesn't exist, a class is missing. Usually caused by a plugin or PHP version incompatibility.
• PHP Warning: Non-critical issue that the code handled, but it indicates sloppy code or an outdated plugin.
• PHP Deprecated: A function that used to work is scheduled for removal in a future PHP version. Safe for now, but worth noting.

Step 4: Disable Debug Mode When Done

Once you have identified and fixed the issue, immediately return to wp-config.php and set all debug constants back:

define( 'WP_DEBUG', false );
define( 'WP_DEBUG_LOG', false );
define( 'WP_DEBUG_DISPLAY', false );

Also delete the debug.log file from wp-content/ — it can grow very large and contains sensitive path information.