WP_Customize_Manager::handle_override_changeset_lock_request(): never

Compatibility

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

Return value

never

Performance profile

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

33–61

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

Plugin surface

None

Nothing here hands control to plugin code.

Called by

0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

• hookthird-party callbacksdo_action()one call below WP_Customize_Manager::handle_override_changeset_lock_request()

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 · 16 distinct outcomes

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

Uses · 9

• wp_send_json_error()Sends a JSON response back to an Ajax request, indicating failure.
• check_ajax_referer()Verifies the Ajax request to prevent processing requests external of the blog.
• __()Retrieves the translation of $text.
• current_user_can()Returns whether the current user has the specified capability.
• get_post_type_object()Retrieves a post type object by name.
• wp_send_json_success()Sends a JSON response back to an Ajax request, indicating success.
• WP_Customize_Manager::is_preview()Determines whether it is a theme preview or not.
• WP_Customize_Manager::changeset_post_id()Gets the changeset post ID for the loaded changeset.
• WP_Customize_Manager::set_changeset_lock()Marks the changeset post as being currently edited by the current user.

Source code

View on Trac ↗View on GitHub ↗

3392	public function handle_override_changeset_lock_request() {3393		if ( ! $this->is_preview() ) {3394			wp_send_json_error( 'not_preview', 400 );3395		}3396 3397		if ( ! check_ajax_referer( 'customize_override_changeset_lock', 'nonce', false ) ) {3398			wp_send_json_error(3399				array(3400					'code'    => 'invalid_nonce',3401					'message' => __( 'Security check failed.' ),3402				)3403			);3404		}3405 3406		$changeset_post_id = $this->changeset_post_id();3407 3408		if ( empty( $changeset_post_id ) ) {3409			wp_send_json_error(3410				array(3411					'code'    => 'no_changeset_found_to_take_over',3412					'message' => __( 'No changeset found to take over' ),3413				)3414			);3415		}3416 3417		if ( ! current_user_can( get_post_type_object( 'customize_changeset' )->cap->edit_post, $changeset_post_id ) ) {3418			wp_send_json_error(3419				array(3420					'code'    => 'cannot_remove_changeset_lock',3421					'message' => __( 'Sorry, you are not allowed to take over.' ),3422				)3423			);3424		}3425 3426		$this->set_changeset_lock( $changeset_post_id, true );3427 3428		wp_send_json_success( 'changeset_taken_over' );3429	}

Changelog

Introduced in 4.9.0. One change between 6.7.7 and 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 7.1.0 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.