wppaste
WordPress

_update_posts_count_on_transition_post_status( string $new_status, string $old_status, WP_Post $post = null )

Since
4.0.0, 4.9.0
Source
wp-includes/ms-blogs.php:911
Handler for updating the current site's posts count when a post status changes.

Compatibility

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

$new_statusstring
The status the post is changing to.
$old_statusstring
The status the post is changing from.
$postWP_Postoptional
Post objectDefault: null

Performance profile

How much work a call to _update_posts_count_on_transition_post_status() 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
Heavy

Reaches the database via get_post().

Scaling
Constant

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

Instructions
6–17

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

  • querycontent queryget_post()one call below _update_posts_count_on_transition_post_status()
  • optionoption read or writeupdate_option()one call below _update_posts_count_on_transition_post_status()

Further down the call graph this can also reach hook, serialize, cache and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 3 distinct outcomes

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

WhenInstructionsCalls it makes
$new_status === false6none
$new_status !== false11–15get_post_type()
$new_status !== false15–17get_post_type(), update_posts_count()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 20 instructions, 6–17 executed per call, 4 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.

Uses · 2

Source code

View on Trac View on GitHub 

function _update_posts_count_on_transition_post_status( $new_status, $old_status, $post = null ) {	if ( $new_status === $old_status ) {		return;	} 	if ( 'post' !== get_post_type( $post ) ) {		return;	} 	if ( 'publish' !== $new_status && 'publish' !== $old_status ) {		return;	} 	update_posts_count();}

Changelog

Introduced in 4.0.0. One change between 6.7.7 and 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.

7.0.4
Parameter $post retyped from WP_Post to WP_Post|null.verified against source
4.9.0
Added the $post parameter.from the docblock
4.0.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 6.8.8 tag, from src/wp-includes/ms-blogs.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.