Language_Pack_Upgrader::async_upgrade( false|WP_Upgrader $upgrader = false )
- Since
- 3.7.0
- Source
wp-admin/includes/class-language-pack-upgrader.php:49
Description
Hooked to the 'upgrader_process_complete' action by default.
Compatibility
- WordPress
- since 3.7.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
$upgraderfalse|WP_Upgraderoptional- WP_Upgrader instance or false. If
$upgraderis a Language_Pack_Upgrader instance, the method will bail to avoid recursion. Otherwise unused. Default false.Default:false
Performance profile
How much work a call to Language_Pack_Upgrader::async_upgrade() 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
- Scaling
- Scales with input
- Instructions
- 5–37
- Plugin surface
- 1 hook
- Called by
- 0
Reads stored settings via get_site_transient(), cached per request but not free on a cold cache.
The body loops, so the work grows with what you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 56.
Third-party callbacks on 'async_update_translation' run inside this call, and their cost is not bounded by anything here.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- hookthird-party callbacks
apply_filters()called directly - transienttransient
get_site_transient()one call below Language_Pack_Upgrader::async_upgrade()
Further down the call graph this can also reach cache, option, serialize and query. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.
What one call costs · 4 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost Language_Pack_Upgrader::async_upgrade() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
$upgrader instanceof | 5 | none |
| always | 7–9 | wp_get_translation_updates() |
| always | 15–22 | wp_get_translation_updates(), ->is_vcs_checkout() |
!->is_vcs_checkout() && !empty($language_updates) | 31–37 | wp_get_translation_updates(), ->is_vcs_checkout(), ->bulk_upgrade() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 56 instructions, 5–37 executed per call, 10 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 Language_Pack_Upgrader::async_upgrade() runs, in this order:
- apply_filters( async_update_translation )filterline 81 (+32 into the body)
Filters whether to asynchronously update translation for core, a plugin, or a theme.
Uses · 5
- wp_get_translation_updates()Retrieves a list of all language updates available.
- apply_filters()Calls the callback functions that have been added to a filter hook.
- WP_Automatic_Updater::__construct()
- Language_Pack_Upgrader_Skin::__construct()Constructor.
- Language_Pack_Upgrader::__construct()
Source code
public static function async_upgrade( $upgrader = false ) { // Avoid recursion. if ( $upgrader && $upgrader instanceof Language_Pack_Upgrader ) { return; } // Nothing to do? $language_updates = wp_get_translation_updates(); if ( ! $language_updates ) { return; } /* * Avoid messing with VCS installations, at least for now. * Noted: this is not the ideal way to accomplish this. */ $check_vcs = new WP_Automatic_Updater(); if ( $check_vcs->is_vcs_checkout( WP_CONTENT_DIR ) ) { return; } foreach ( $language_updates as $key => $language_update ) { $update = ! empty( $language_update->autoupdate ); /** * Filters whether to asynchronously update translation for core, a plugin, or a theme. * * @since 4.0.0 * * @param bool $update Whether to update. * @param object $language_update The update offer. */ $update = apply_filters( 'async_update_translation', $update, $language_update ); if ( ! $update ) { unset( $language_updates[ $key ] ); } } if ( empty( $language_updates ) ) { return; } // Re-use the automatic upgrader skin if the parent upgrader is using it. if ( $upgrader && $upgrader->skin instanceof Automatic_Upgrader_Skin ) { $skin = $upgrader->skin; } else { $skin = new Language_Pack_Upgrader_Skin( array( 'skip_header_footer' => true, ) ); } $lp_upgrader = new Language_Pack_Upgrader( $skin ); $lp_upgrader->bulk_upgrade( $language_updates ); }Changelog
Introduced in 3.7.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-admin/includes/class-language-pack-upgrader.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.