wppaste
WordPress

wp_xmlrpc_server::pingback_error( int $code, string $message ): IXR_Error

Since
3.6.0
Source
wp-includes/class-wp-xmlrpc-server.php:7216
Sends a pingback error based on the given error code and message.

Compatibility

WordPress
since 3.6.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

$codeint
Error code.
$messagestring
Error message.

Return value

IXR_Error
Error object.

Performance profile

How much work a call to wp_xmlrpc_server::pingback_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
11

Executed per call on PHP 8.5. The body compiles to 11.

Plugin surface
1 hook

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

Called by
2

2 places 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 · 1 distinct outcome

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

WhenInstructionsCalls it makes
always11apply_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: 11 instructions, 11 executed per call, 0 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_xmlrpc_server::pingback_error() runs, in this order:

  1. apply_filters( xmlrpc_pingback_error )filterline 7224 (+8 into the body)

    Filters the XML-RPC pingback error return.

Uses · 2

Used by · 2

Source code

View on Trac View on GitHub 

	protected function pingback_error( $code, $message ) {		/**		 * Filters the XML-RPC pingback error return.		 *		 * @since 3.5.1		 *		 * @param IXR_Error $error An IXR_Error object containing the error code and message.		 */		return apply_filters( 'xmlrpc_pingback_error', new IXR_Error( $code, $message ) );	}

Changelog

Introduced in 3.6.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.8.8 tag, from src/wp-includes/class-wp-xmlrpc-server.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.