wppaste
WordPress

wp_get_auto_update_message(): string

Since
5.5.0
Source
wp-admin/includes/update.php:1099
Determines the appropriate auto-update message to be displayed.

Compatibility

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

Return value

string
The update message to be shown.

Performance profile

How much work a call to wp_get_auto_update_message() 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–25

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

Plugin surface
None

Nothing here hands control to plugin code.

Called by
6

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

What it touches

  • hookthird-party callbacksapply_filters()one call below wp_get_auto_update_message()

Further down the call graph this can also reach option, cache, serialize, query 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 · 2 distinct outcomes

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

WhenInstructionsCalls it makes
$next_update_time === false11wp_next_scheduled(), __()
$next_update_time !== false25wp_next_scheduled(), human_time_diff(), time(), __(), sprintf()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 39 instructions, 11–25 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.

Uses · 3

Used by · 6

Source code

function wp_get_auto_update_message() {	$next_update_time = wp_next_scheduled( 'wp_version_check' ); 	// Check if the event exists.	if ( false === $next_update_time ) {		$message = __( 'Automatic update not scheduled. There may be a problem with WP-Cron.' );	} else {		$time_to_next_update = human_time_diff( (int) $next_update_time ); 		// See if cron is overdue.		$overdue = ( time() - $next_update_time ) > 0; 		if ( $overdue ) {			$message = sprintf(				/* translators: %s: Duration that WP-Cron has been overdue. */				__( 'Automatic update overdue by %s. There may be a problem with WP-Cron.' ),				$time_to_next_update			);		} else {			$message = sprintf(				/* translators: %s: Time until the next update. */				__( 'Automatic update scheduled in %s.' ),				$time_to_next_update			);		}	} 	return $message;}

Changelog

Introduced in 5.5.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-admin/includes/update.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.