• Resolved peter8nss

    (@peter8nss)


    Function wp_update_https_detection_errors is marked as deprecated but is still used by function wp_is_https_supported.

    Think this is triggered from cron job wp_site_health_scheduled_check. I think it will only occur on the first run of this after a new installation if option https_detection_errors is not already set. After that, option https_detection_errors will be set, and the call to wp_update_https_detection_errors will be bypassed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter peter8nss

    (@peter8nss)

    Not sure where the “However, it may still be called during initial site health checks” comes from. Documentation for wp_update_https_detection_errors function says:

    This function has been deprecated. The 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 instead.

    It looks like this usage was missed when deprecating the function and would need to be fixed before the function could actually be removed. Hence, why I was raising this.

    Moderator James Huff

    (@macmanx)

    Please ignore the earlier reply. It was just a spammer using ChatGPT to make something that looked like a valid reply.

    In this case, please report the bug you found following the steps at https://make.www.ads-software.com/core/handbook/testing/reporting-bugs/

    Thanks!

    Thread Starter peter8nss

    (@peter8nss)

    Moderator James Huff

    (@macmanx)

    You’re welcome!

    Discussion continues in that ticket.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘wp_is_https_supported uses deprecated function’ is closed to new replies.