wp_update_https_detection_errors()
- Since
- 5.7.0
- Source
wp-includes/deprecated.php:5989
Description
This internal function is called by a regular Cron hook to ensure HTTPS support is detected and maintained.
Compatibility
Deprecated in WordPress 6.4.0. The <code>wp_update_https_detection_errors()</code> function is no longer used and has been replaced by <code>wp_get_https_detection_errors()</code>. Previously the function was called by a regular Cron hook to update the <code>https_detection_errors</code> option, but this is no longer necessary as the errors are retrieved directly in Site Health and no longer used outside of Site Health.
- WordPress
- since 5.7.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_update_https_detection_errors() 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
- Expensive
- Scaling
- Constant
- Instructions
- 21
- Plugin surface
- 1 hook
- Called by
- 0
Reaches an outbound HTTP request via wp_remote_request().
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 29.
Third-party callbacks on 'pre_wp_update_https_detection_errors' run inside this call, and their cost is not bounded by anything here.
Nothing in core calls this; the cost is only what you spend yourself.
What it touches
- hookthird-party callbacks
apply_filters()called directly - optionoption read or write
update_option()called directly - serializeserialisation
maybe_serialize()one call below wp_update_https_detection_errors() - cacheobject cache
wp_cache_get()one call below wp_update_https_detection_errors() - httpoutbound HTTP request
wp_remote_request()one call below wp_update_https_detection_errors()
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 · 2 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_update_https_detection_errors() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
is_wp_error() | 21 | _deprecated_function(), apply_filters(), is_wp_error(), update_option() |
!is_wp_error() | 21 | _deprecated_function(), apply_filters(), is_wp_error(), wp_get_https_detection_errors(), update_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: 29 instructions, 21 executed per call, 1 branch. 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.
Hooks and filters fired · 1
One hook fires while wp_update_https_detection_errors() runs, in this order:
- apply_filters( pre_wp_update_https_detection_errors )filterline 6004 (+15 into the body)
Short-circuits the process of detecting errors related to HTTPS support.
Uses · 5
- _deprecated_function()Marks a function as deprecated and inform when it has been used.
- apply_filters()Calls the callback functions that have been added to a filter hook.
- is_wp_error()Checks whether the given variable is a WordPress Error.
- update_option()Updates the value of an option that was already added.
- wp_get_https_detection_errors()Runs a remote HTTPS request to detect whether HTTPS supported, and stores potential errors.
Source code
function wp_update_https_detection_errors() { _deprecated_function( __FUNCTION__, '6.4.0' ); /** * Short-circuits the process of detecting errors related to HTTPS support. * * Returning a `WP_Error` from the filter will effectively short-circuit the default logic of trying a remote * request to the site over HTTPS, storing the errors array from the returned `WP_Error` instead. * * @since 5.7.0 * @deprecated 6.4.0 The `wp_update_https_detection_errors` filter is no longer used and has been replaced by `pre_wp_get_https_detection_errors`. * * @param null|WP_Error $pre Error object to short-circuit detection, * or null to continue with the default behavior. */ $support_errors = apply_filters( 'pre_wp_update_https_detection_errors', null ); if ( is_wp_error( $support_errors ) ) { update_option( 'https_detection_errors', $support_errors->errors, false ); return; } $support_errors = wp_get_https_detection_errors(); update_option( 'https_detection_errors', $support_errors );}Changelog
Introduced in 5.7.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
wp_update_https_detection_errors() function is no longer used and has been replaced by wp_get_https_detection_errors(). Previously the function was called by a regular Cron hook to update the https_detection_errors option, but this is no longer necessary as the errors are retrieved directly in Site Health and no longer used outside of Site Health.from the docblockAbout this page
- Parsed data
- Generated from the wordpress-develop 6.9.7 tag, from
src/wp-includes/deprecated.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.