Allow error_reporting level to be configurable for WP_DEBUG

[luistar15]

I use WP_DEBUG_LOG in production to catch errors not caught during development.
But almost all entries are PHP Deprecated errors. This makes hard to spot more relevant errors.

It would be useful to be able to configure the error level report when using WP_DEBUG.

[luistar15]

In the mean time I have modified the wp_debug_mode() function to acomplish what I need

[knutsp]

Could this be combined into one constant? When WP_DEBUG is integer, use as error_level, otherwise truthy /falsey as currently. A few other constants work in a similar way.

[luistar15]

Replying to knutsp:

Could this be combined into one constant? When WP_DEBUG is integer, use as error_level, otherwise truthy /falsey as currently. A few other constants work in a similar way.

I wouldn't mind that. But personally a prefer multiple explicit settings rather that one that could mean many things.

The new constant WP_DEBUG_ERROR_LEVEL can be set from wp-config.php to override the E_ALL level forced in wp_debug_mode() .

Trac ticket: https://core.trac.wordpress.org/ticket/56252

[mikebricknellbarlow]

Seconding this request - just been configuring my local dev environment so that I can leave WP_DEBUG turned on, but only see breaking errors. I ended up implementing the same solution as @luistar15, and actually came here to suggest it until I saw it was already here.

This would be a great help for agency developers like myself, who don't need to be seeing 100s of deprecated warnings from Core and plugins while trying to debug custom code.

[flixos90]

@jorbin Since you were among the last people to touch wp_debug_mode() (only 9 years ago 😂), it would be great to get your feedback about this proposed enhancement.

The PR looks good to me for what it's supposed to achieve, but it would be good to get input on the idea from a long-term component maintainer like you.

[jorbin]

My first reaction: "I touched wp_debug_mode?"

My second thought: I think this is a duplicate of #31839. As there is a bit more discussion on that ticket, I think we should close this one and focus on that one. I'll throw a bit more there, but in general I can get behind making this configurable. It's going to require some documentation though since error_reporting will fatal if you pass in a non-integar. I don't think we need to go so far as to put in guard rails if you pass in a something besides an int, but I do think some documentation to help folks who cause a fatal is necessary.

[pbearne]

Duplicate of #31839.