WP_Recovery_Mode_Key_Service::get_keys(): array
- Since
- 5.2.0, 6.8.0
- Source
wp-includes/class-wp-recovery-mode-key-service.php:167
Compatibility
- WordPress
- since 6.8.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.
Return value
array- Associative array of token => data pairs, where the data is an associative array of information about the key.
...$0arrayInformation about the key.$hashed_keystringThe hashed value of the key.$created_atintThe timestamp when the key was created.
Performance profile
How much work a call to WP_Recovery_Mode_Key_Service::get_keys() 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
- Moderate
- Scaling
- Constant
- Instructions
- 8
- Plugin surface
- None
- Called by
- 4
Reads stored settings via get_option(), cached per request but not free on a cold cache.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5. The body compiles to 8.
Nothing here hands control to plugin code.
4 places in core call this, so the cost is paid more often than your own code shows.
What it touches
- optionoption read or write
get_option()called directly - hookthird-party callbacks
apply_filters()one call below WP_Recovery_Mode_Key_Service::get_keys() - cacheobject cache
wp_cache_get()one call below WP_Recovery_Mode_Key_Service::get_keys() - serializeserialisation
maybe_unserialize()one call below WP_Recovery_Mode_Key_Service::get_keys()
Further down the call graph this can also reach 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 · 1 distinct outcome
One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Recovery_Mode_Key_Service::get_keys() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
| always | 8 | get_option() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 8 instructions, 8 executed per call, 0 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 · 1
- get_option()Retrieves an option value based on an option name.
Used by · 4
- WP_Recovery_Mode_Key_Service::clean_expired_keys()Removes expired recovery mode keys.
- WP_Recovery_Mode_Key_Service::generate_and_store_recovery_mode_key()Creates a recovery mode key.
- WP_Recovery_Mode_Key_Service::remove_key()Removes a used recovery key.
- WP_Recovery_Mode_Key_Service::validate_recovery_mode_key()Verifies if the recovery mode key is correct.
Source code
private function get_keys() { return (array) get_option( $this->option_name, array() ); }Changelog
Introduced in 5.2.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
Existing keys may still be hashed using phpass.from the docblock
About this page
- Parsed data
- Generated from the wordpress-develop 7.1.0 tag, from
src/wp-includes/class-wp-recovery-mode-key-service.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.