Why WP_DEBUG_DISPLAY Should Be Disabled on Live Sites

Why displaying PHP and WordPress notices to visitors can expose paths, queries and implementation details.

Why this check matters

A notice that helps a developer can confuse a visitor and disclose information useful to an attacker. Logging and display are separate controls and should be treated separately.

How to review it

  1. Check whether WP_DEBUG_DISPLAY is enabled.
  2. Keep errors in a protected log when troubleshooting is required.
  3. Test a public page while logged out after changing the setting.
  4. Review the log and remove sensitive diagnostic data.

Keep the change safe

Do not suppress every error blindly. Fix the underlying warning, keep display off, and use a controlled log for diagnosis.

How WPVitals uses this signal

WPVitals checks this setting locally and reports the result in the WordPress dashboard. The check is a maintenance signal, so review the site context before changing a setting and test the visitor experience afterwards.

Dealing with something like this?

We are happy to give an honest read on it before anyone writes a proposal. No obligation, and we will tell you if the answer is that you do not need us.

Start a project

Tell us about your project. We’ll get back within 24 hours with a clear assessment and timeline.

Get in touch

Quick question? Send us a message.