wppaste
WordPress

WP_Fatal_Error_Handler::should_handle_error( array $error ): bool

Since
5.2.0
Source
wp-includes/class-wp-fatal-error-handler.php:100
Determines whether we are dealing with an error that WordPress should handle in order to protect the admin backend against WSODs.

Compatibility

WordPress
since 5.2.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$errorarray
Error information retrieved from error_get_last().

Return value

bool
Whether WordPress should handle this error.

Performance profile

How much work a call to WP_Fatal_Error_Handler::should_handle_error() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
7–13

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 14.

Plugin surface
1 hook

Third-party callbacks on 'wp_should_handle_php_error' run inside this call, and their cost is not bounded by anything here.

Called by
1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly

What one call costs · 2 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Fatal_Error_Handler::should_handle_error() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
isset($error)7none
always10–13apply_filters()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 14 instructions, 7–13 executed per call, 2 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Hooks and filters fired · 1

One hook fires while WP_Fatal_Error_Handler::should_handle_error() runs, in this order:

  1. apply_filters( wp_should_handle_php_error )filterline 125 (+25 into the body)

    Filters whether a given thrown error should be handled by the fatal error handler.

Uses · 1

  • apply_filters()Calls the callback functions that have been added to a filter hook.

Used by · 1

Source code

	protected function should_handle_error( $error ) {		$error_types_to_handle = array(			E_ERROR,			E_PARSE,			E_USER_ERROR,			E_COMPILE_ERROR,			E_RECOVERABLE_ERROR,		); 		if ( isset( $error['type'] ) && in_array( $error['type'], $error_types_to_handle, true ) ) {			return true;		} 		/**		 * Filters whether a given thrown error should be handled by the fatal error handler.		 *		 * This filter is only fired if the error is not already configured to be handled by WordPress core. As such,		 * it exclusively allows adding further rules for which errors should be handled, but not removing existing		 * ones.		 *		 * @since 5.2.0		 *		 * @param bool  $should_handle_error Whether the error should be handled by the fatal error handler.		 * @param array $error               Error information retrieved from `error_get_last()`.		 */		return (bool) apply_filters( 'wp_should_handle_php_error', false, $error );	}

Changelog

Introduced in 5.2.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data
Generated from the wordpress-develop 6.7.7 tag, from src/wp-includes/class-wp-fatal-error-handler.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.