WP_Session_Tokens::update_session( string $verifier, array $session = null )
- Since
- 4.0.0
- Source
wp-includes/class-wp-session-tokens.php:266
Description
Omitting the second argument destroys the session.
Compatibility
- WordPress
- since 4.0.0
- 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).
Parameters
$verifierstring- Verifier for the session to update.
$sessionarrayoptional- Session. Omitting this argument destroys the session.Default:
null
Performance profile
How much work a call to WP_Session_Tokens::update_session() 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
- Plugin surface
- None
- Called by
- 2
Touches nothing outside its own arguments.
No loop in the body: the same number of instructions runs whatever you pass in.
Nothing here hands control to plugin code.
2 places in core call this, so the cost is paid more often than your own code shows.
Used by · 2
- WP_Session_Tokens::destroy()Destroys the session with the given token.
- WP_Session_Tokens::update()Updates the data for the session with the given token.
Source code
abstract protected function update_session( $verifier, $session = null );Changelog
Introduced in 4.0.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-includes/class-wp-session-tokens.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.