WP_Customize_Manager::set_changeset_lock( int $changeset_post_id, bool $take_over = false )
- Since
- 4.9.0
- Source
wp-includes/class-wp-customize-manager.php:3255
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
$changeset_post_idint- Changeset post ID.
$take_overbooloptional- Whether to take over the changeset. Default false.Default:
false
Performance profile
How much work a call to WP_Customize_Manager::set_changeset_lock() 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
- Scaling
- Constant
- Instructions
- 4–25
- Plugin surface
- None
- Called by
- 3
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 29.
Nothing here hands control to plugin code.
3 places in core call this, so the cost is paid more often than your own code shows.
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 WP_Customize_Manager::set_changeset_lock() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 4 | none |
| always | 15–16 | get_post_meta(), ->refresh_changeset_lock() |
| always | 24–25 | get_post_meta(), time(), get_current_user_id(), update_post_meta() |
Across PHP versions
| PHP | Compiled | Executed | Branches | Notes |
|---|---|---|---|---|
| 8.6-dev | 29 | 4–25 | 3 | |
| 8.5 | 29 | 4–25 | 3 | |
| 8.4 | 29 | 4–25 | 3 | 3 fewer instructions than PHP 8.3 |
| 8.3 | 32 | 4–28 | 3 | |
| 8.2 | 32 | 4–28 | 3 | |
| 8.1 | 32 | 4–28 | 3 | |
| 7.4 | 32 | 4–28 | 3 |
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 · 4
- get_post_meta()Retrieves a post meta field for the given post ID.
- get_current_user_id()Gets the current user's ID.
- update_post_meta()Updates a post meta field based on the given post ID.
- WP_Customize_Manager::refresh_changeset_lock()Refreshes changeset lock with the current time if current user edited the changeset before.
Used by · 3
- WP_Customize_Manager::establish_loaded_changeset()Establishes the loaded changeset.
- WP_Customize_Manager::handle_override_changeset_lock_request()Removes changeset lock when take over request is sent via Ajax.
- WP_Customize_Manager::save()Handles customize_save WP Ajax request to save/update a changeset.
Source code
public function set_changeset_lock( $changeset_post_id, $take_over = false ) { if ( $changeset_post_id ) { $can_override = ! (bool) get_post_meta( $changeset_post_id, '_edit_lock', true ); if ( $take_over ) { $can_override = true; } if ( $can_override ) { $lock = sprintf( '%s:%s', time(), get_current_user_id() ); update_post_meta( $changeset_post_id, '_edit_lock', $lock ); } else { $this->refresh_changeset_lock( $changeset_post_id ); } } }Changelog
Introduced in 4.9.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.9.7 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.