Open hawkidoki opened 9 months ago
I don't believe that was intended, but you're right, it is a consequence.
Currently, the error is only prevented if the current user can view QM, which means that visits without QM visible will still be logged. Unless QM is visible to all users?
Hello,
I would to report an issue. It's not really a bug tho, as I believe this is an intended behavior since the rework of
_doing_it_wrong()
,_deprecated_function()
etc... handling in a recent update this summer (see #739).Since this patch, any
_doing_it_wrong()
,_deprecated_function()
thrown by the WP core aren't logged in PHP logs file or in/wp-content/debug.log
whenWP_DEBUG_LOG
is enabled. It seems that only QM is able to catch them.I believe QM should leave errors in logs file and not hijack them, as many developers watch the error logs file when coding. Sure, it is nice to have a separate tab in QM for "Doing it wrong", but QM admin bar is not always available (in ajax queries etc...) which means some "Doing it wrong" could be never seen.
As developers, we need to trust our PHP logs as the ultimate source of truth when it comes to errors/warnings/notices.
Steps to reproduce:
With QM enabled:
Without QM:
Thanks! Regards.