WP_Automatic_Updater::after_core_update( object $update_result )

Compatibility

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

Parameters

$update_resultobject

The result of the core update. Includes the update offer and result.

Performance profile

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

Moderate

Reads stored settings via update_site_option(), cached per request but not free on a cold cache.

Scaling

Constant

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

Instructions

15–92

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

Plugin surface

None

Nothing here hands control to plugin code.

Called by

1

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

What it touches

• optionnetwork optionupdate_site_option()called directly
• hookthird-party callbacksdo_action()one call below WP_Automatic_Updater::after_core_update()

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

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

Uses · 7

• wp_get_wp_version()Returns the current WordPress version.
• is_wp_error()Checks whether the given variable is a WordPress Error.
• str_contains()Polyfill for `str_contains()` function added in PHP 8.0.
• update_site_option()Updates the value of an option that was already added for the current network.
• get_site_option()Retrieve an option value for the current network based on name of option.
• wp_schedule_single_event()Schedules an event to run only once.
• WP_Automatic_Updater::send_email()Sends an email upon the completion or failure of a background core update.

Used by · 1

• WP_Automatic_Updater::run()Kicks off the background update process, looping through all pending updates.

Source code

View on Trac ↗View on GitHub ↗

797	protected function after_core_update( $update_result ) {798		$wp_version = wp_get_wp_version();799 800		$core_update = $update_result->item;801		$result      = $update_result->result;802 803		if ( ! is_wp_error( $result ) ) {804			$this->send_email( 'success', $core_update );805			return;806		}807 808		$error_code = $result->get_error_code();809 810		/*811		 * Any of these WP_Error codes are critical failures, as in they occurred after we started to copy core files.812		 * We should not try to perform a background update again until there is a successful one-click update performed by the user.813		 */814		$critical = false;815		if ( 'disk_full' === $error_code || str_contains( $error_code, '__copy_dir' ) ) {816			$critical = true;817		} elseif ( 'rollback_was_required' === $error_code && is_wp_error( $result->get_error_data()->rollback ) ) {818			// A rollback is only critical if it failed too.819			$critical        = true;820			$rollback_result = $result->get_error_data()->rollback;821		} elseif ( str_contains( $error_code, 'do_rollback' ) ) {822			$critical = true;823		}824 825		if ( $critical ) {826			$critical_data = array(827				'attempted'  => $core_update->current,828				'current'    => $wp_version,829				'error_code' => $error_code,830				'error_data' => $result->get_error_data(),831				'timestamp'  => time(),832				'critical'   => true,833			);834			if ( isset( $rollback_result ) ) {835				$critical_data['rollback_code'] = $rollback_result->get_error_code();836				$critical_data['rollback_data'] = $rollback_result->get_error_data();837			}838			update_site_option( 'auto_core_update_failed', $critical_data );839			$this->send_email( 'critical', $core_update, $result );840			return;841		}842 843		/*844		 * Any other WP_Error code (like download_failed or files_not_writable) occurs before845		 * we tried to copy over core files. Thus, the failures are early and graceful.846		 *847		 * We should avoid trying to perform a background update again for the same version.848		 * But we can try again if another version is released.849		 *850		 * For certain 'transient' failures, like download_failed, we should allow retries.851		 * In fact, let's schedule a special update for an hour from now. (It's possible852		 * the issue could actually be on WordPress.org's side.) If that one fails, then email.853		 */854		$send               = true;855		$transient_failures = array( 'incompatible_archive', 'download_failed', 'insane_distro', 'locked' );856		if ( in_array( $error_code, $transient_failures, true ) && ! get_site_option( 'auto_core_update_failed' ) ) {857			wp_schedule_single_event( time() + HOUR_IN_SECONDS, 'wp_maybe_auto_update' );858			$send = false;859		}860 861		$notified = get_site_option( 'auto_core_update_notified' );862 863		// Don't notify if we've already notified the same email address of the same version of the same notification type.864		if ( $notified865			&& 'fail' === $notified['type']866			&& get_site_option( 'admin_email' ) === $notified['email']867			&& $notified['version'] === $core_update->current868		) {869			$send = false;870		}871 872		update_site_option(873			'auto_core_update_failed',874			array(875				'attempted'  => $core_update->current,876				'current'    => $wp_version,

Changelog

Introduced in 3.7.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.9.7 tag, from src/wp-admin/includes/class-wp-automatic-updater.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.