wp_xmlrpc_server::_prepare_term( array|object $term ): array

Compatibility

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

Parameters

$termarray|object

The unprepared term data.

Return value

array

The prepared term data.

Performance profile

How much work a call to wp_xmlrpc_server::_prepare_term() 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

37–41

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

Plugin surface

1 hook

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

Called by

3

3 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 · 2 distinct outcomes

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

Hooks and filters fired · 1

One hook fires while wp_xmlrpc_server::_prepare_term() runs, in this order:

1. 1
   apply_filters( xmlrpc_prepare_term )filterline 880 (+26 into the body)

   Filters XML-RPC-prepared data for the given term.

Uses · 2

• apply_filters()Calls the callback functions that have been added to a filter hook.
• wp_xmlrpc_server::get_term_custom_fields()Retrieves custom fields for a term.

Used by · 3

• wp_xmlrpc_server::_prepare_post()Prepares post data for return in an XML-RPC object.
• wp_xmlrpc_server::wp_getTerm()Retrieves a term.
• wp_xmlrpc_server::wp_getTerms()Retrieves all terms for a taxonomy.

Source code

View on Trac ↗View on GitHub ↗

854	protected function _prepare_term( $term ) {855		$_term = $term;856		if ( ! is_array( $_term ) ) {857			$_term = get_object_vars( $_term );858		}859 860		// For integers which may be larger than XML-RPC supports ensure we return strings.861		$_term['term_id']          = (string) $_term['term_id'];862		$_term['term_group']       = (string) $_term['term_group'];863		$_term['term_taxonomy_id'] = (string) $_term['term_taxonomy_id'];864		$_term['parent']           = (string) $_term['parent'];865 866		// Count we are happy to return as an integer because people really shouldn't use terms that much.867		$_term['count'] = (int) $_term['count'];868 869		// Get term meta.870		$_term['custom_fields'] = $this->get_term_custom_fields( $_term['term_id'] );871 872		/**873		 * Filters XML-RPC-prepared data for the given term.874		 *875		 * @since 3.4.0876		 *877		 * @param array        $_term An array of term data.878		 * @param array|object $term  Term object or array.879		 */880		return apply_filters( 'xmlrpc_prepare_term', $_term, $term );881	}

Changelog

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.