WP_Customize_Manager::enqueue_control_scripts()
- Since
- 3.4.0
- Source
wp-includes/class-wp-customize-manager.php:4553
Compatibility
- WordPress
- since 3.4.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.
Performance profile
How much work a call to WP_Customize_Manager::enqueue_control_scripts() 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
- 7–31
- Plugin surface
- None
- 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 how much data it finds.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 34.
Nothing here hands control to plugin code.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- transienttransient
get_site_transient()one call below WP_Customize_Manager::enqueue_control_scripts() - hookthird-party callbacks
apply_filters()one call below WP_Customize_Manager::enqueue_control_scripts()
Further down the call graph this can also reach cache, option, query and serialize. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.
What one call costs · 5 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Customize_Manager::enqueue_control_scripts() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
is_multisite() | 7–8 | is_multisite() |
!is_multisite() && !current_user_can() | 19–20 | is_multisite(), current_user_can(), current_user_can(), current_user_can() |
!is_multisite() && current_user_can() | 22–23 | is_multisite(), current_user_can(), wp_enqueue_script(), wp_get_update_data(), totals() |
!is_multisite() | 26–27 | is_multisite(), current_user_can(), current_user_can(), wp_enqueue_script(), wp_get_update_data(), totals() |
!is_multisite() | 30–31 | is_multisite(), current_user_can(), current_user_can(), current_user_can(), wp_enqueue_script(), wp_get_update_data(), totals() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 34 instructions, 7–31 executed per call, 6 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 · 5
- is_multisite()Determines whether Multisite is enabled.
- current_user_can()Returns whether the current user has the specified capability.
- wp_enqueue_script()Enqueues a script.
- wp_localize_script()Localizes a script.
- wp_get_update_data()Collects counts and UI strings for available updates.
Source code
public function enqueue_control_scripts() { foreach ( $this->controls as $control ) { $control->enqueue(); } if ( ! is_multisite() && ( current_user_can( 'install_themes' ) || current_user_can( 'update_themes' ) || current_user_can( 'delete_themes' ) ) ) { wp_enqueue_script( 'updates' ); wp_localize_script( 'updates', '_wpUpdatesItemCounts', array( 'totals' => wp_get_update_data(), ) ); } }Changelog
Introduced in 3.4.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 6.8.8 tag, from
src/wp-includes/class-wp-customize-manager.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.