wp_ajax_destroy_sessions()
- Since
- 4.1.0
- Source
wp-admin/includes/ajax-actions.php:4008
Compatibility
- WordPress
- since 4.1.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_ajax_destroy_sessions() 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
- Constant
- Instructions
- 41–61
- Plugin surface
- None
- Called by
- 0
Reaches the database via get_user_by().
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 73.
Nothing here hands control to plugin code.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- querycontent query
get_user_by()one call below wp_ajax_destroy_sessions() - hookthird-party callbacks
apply_filters()one call below wp_ajax_destroy_sessions()
Further down the call graph this can also reach option, cache, serialize 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 · 10 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_ajax_destroy_sessions() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 41 | get_userdata(), __(), message(), ::WP_Session_Tokens(), get_current_user_id(), wp_get_session_token(), ->destroy_others(), __(), message() |
| always | 42 | get_userdata(), __(), message(), ::WP_Session_Tokens(), get_current_user_id(), ->destroy_all(), __(), sprintf(), message() |
!current_user_can() | 44 | get_userdata(), current_user_can(), ::WP_Session_Tokens(), get_current_user_id(), wp_get_session_token(), ->destroy_others(), __(), message() |
!current_user_can() | 45 | get_userdata(), current_user_can(), ::WP_Session_Tokens(), get_current_user_id(), ->destroy_all(), __(), sprintf(), message() |
!current_user_can() | 51 | get_userdata(), current_user_can(), __(), message(), ::WP_Session_Tokens(), get_current_user_id(), wp_get_session_token(), ->destroy_others(), __(), message() |
current_user_can() | 52–53 | get_userdata(), current_user_can(), wp_verify_nonce(), ::WP_Session_Tokens(), get_current_user_id(), wp_get_session_token(), ->destroy_others(), __(), message() |
!current_user_can() | 52 | get_userdata(), current_user_can(), __(), message(), ::WP_Session_Tokens(), get_current_user_id(), ->destroy_all(), __(), sprintf(), message() |
current_user_can() | 53–54 | get_userdata(), current_user_can(), wp_verify_nonce(), ::WP_Session_Tokens(), get_current_user_id(), ->destroy_all(), __(), sprintf(), message() |
current_user_can() | 59–60 | get_userdata(), current_user_can(), wp_verify_nonce(), __(), message(), ::WP_Session_Tokens(), get_current_user_id(), wp_get_session_token(), ->destroy_others(), __(), message() |
current_user_can() | 60–61 | get_userdata(), current_user_can(), wp_verify_nonce(), __(), message(), ::WP_Session_Tokens(), get_current_user_id(), ->destroy_all(), __(), sprintf(), message() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 73 instructions, 41–61 executed per call, 5 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 · 9
- get_userdata()Retrieves user info by user ID.
- current_user_can()Returns whether the current user has the specified capability.
- wp_verify_nonce()Verifies that a correct security nonce was used with time limit.
- wp_send_json_error()Sends a JSON response back to an Ajax request, indicating failure.
- __()Retrieves the translation of $text.
- get_current_user_id()Gets the current user's ID.
- wp_get_session_token()Retrieves the current session token from the logged_in cookie.
- wp_send_json_success()Sends a JSON response back to an Ajax request, indicating success.
- WP_Session_Tokens::get_instance()Retrieves a session manager instance for a user.
Source code
function wp_ajax_destroy_sessions() { $user = get_userdata( (int) $_POST['user_id'] ); if ( $user ) { if ( ! current_user_can( 'edit_user', $user->ID ) ) { $user = false; } elseif ( ! wp_verify_nonce( $_POST['nonce'], 'update-user_' . $user->ID ) ) { $user = false; } } if ( ! $user ) { wp_send_json_error( array( 'message' => __( 'Could not log out user sessions. Please try again.' ), ) ); } $sessions = WP_Session_Tokens::get_instance( $user->ID ); if ( get_current_user_id() === $user->ID ) { $sessions->destroy_others( wp_get_session_token() ); $message = __( 'You are now logged out everywhere else.' ); } else { $sessions->destroy_all(); /* translators: %s: User's display name. */ $message = sprintf( __( '%s has been logged out.' ), $user->display_name ); } wp_send_json_success( array( 'message' => $message ) );}Changelog
Introduced in 4.1.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/ajax-actions.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.