debug.log hasn’t written anything since March 15.
Which is odd, since, earlier today, I broke something on purpose and the site displayed… well, it was kind of an elaborate PHP box/table, rather than a one-line PHP read-out… stack-trace/xdebug, I guess.
I just manually added in…
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_DISPLAY’, true );
define( ‘WP_DEBUG_LOG’, true );
I just broke the thing again and, this time, it both echoes the error box and wrote the stack-trace to debug.log. So that shows debug.log is now writing…
So, any errors when I perform WP-Debugging actions… ?
No
In the plugin screen, I check/uncheck box combos and save. The lines destined for writing get updated in the preview box, but a) nothing is added to debug.log and b) …
Hang on… now, when I check/uncheck those boxes, I do see wp-config.php getting amended in real-time.
I guess it works then.
I’m curious…
With WP_DEBUG_DISPLAY true/default, what kinds of output should display versus the stacktrace box, which seems much more detailed? Does presence of the stacktrace box override WP debug display?
Can’t remember how/whether I enabled that PHP box in LocalWP; I don’t have any LocalWP add-ons. Is that the standard verbosity for debug expression in LocalWP?
-
This reply was modified 2 years, 8 months ago by parakeet.
-
This reply was modified 2 years, 8 months ago by parakeet.
-
This reply was modified 2 years, 8 months ago by parakeet.