WP_DEBUG Configurator

Turn on the debug log without breaking your live site

Tumatakbo sa iyong browser. Walang ina-upload.

Where is this site?

This changes the recommendation, not just the wording. The safe configuration on a live site is genuinely different from the useful one on your laptop.

Live site Local / staging

Verdict

—

Options

WP_DEBUG — turn debugging onMakes WordPress report PHP notices, warnings and deprecations it would otherwise swallow. WP_DEBUG_LOG — write to a fileErrors go to wp-content/debug.log instead of the screen. This is the constant that makes debugging on a live site safe. WP_DEBUG_DISPLAY false — hide errors from visitorsWithout this, WP_DEBUG prints PHP errors into your pages. Turning it off is the single most important line on this page. Write the log outside the web rootwp-content/debug.log is publicly readable on many hosts — anyone can just fetch it. Moving it above the web root fixes that. Adjust the path to match your server. SAVEQUERIES — log every database queryUseful for hunting a slow page. Costs memory on EVERY request, so turn it off again afterwards. SCRIPT_DEBUG — load unminified core JS/CSSOnly useful if you are debugging the block editor or core scripts.

wp-config.php

Paste these ABOVE the line that says /* That's all, stop editing! */ — anything below it is ignored, which is why so many people report that WP_DEBUG 'does nothing'.

Tungkol sa WP_DEBUG Configurator

Generate the WP_DEBUG constants that write errors to a log file instead of printing them to your visitors. The default WP_DEBUG snippet most sites copy will display PHP errors publicly — this one will not.

Kaugnay

Iba pang tools na baka kailanganin mo

WordPress PHP Fatal Error Decoder

Paste the error. We name the plugin.

wp-config.php Generator

Build a correct wp-config.php without copy-pasting from a 2014 blog post

FAQ

Mga Tanong

Ligtas bang i-enable ang WP_DEBUG sa isang live na site?

Tanging kung ang WP_DEBUG_DISPLAY ay nakatakda sa false. Nang mag-isa, iprinint ng WP_DEBUG ang PHP notices at warnings — kasama ang absolute file paths ng iyong server — nang direkta sa mga page na nilo-load ng iyong bisita. Halos bawat tutorial ay ibinibigay sa iyo ang isang linyang iyon at huminto. Isama ito sa WP_DEBUG_LOG at WP_DEBUG_DISPLAY na false at ligtas na ito.

Saan napupunta ang WordPress debug log?

wp-content/debug.log bilang default. Sulit malaman: sa maraming host ang file na iyon ay pampublikong makukuha — sinuman ay makakahiling nito sa isang browser. Puwede kang magpasa ng path sa WP_DEBUG_LOG sa halip at isulat ang log sa itaas ng web root, na ibubuo ng tool na ito para sa iyo.

Itinakda ko ang WP_DEBUG sa true at walang nangyari. Bakit?

Halos palaging dahil idinagdag ang constant SA IBABA ng linyang nagsasabing "That's all, stop editing!" sa wp-config.php. Lahat pagkatapos ng linyang iyon ay hindi pinapansin. Ilipat ito sa itaas.