Make WordPress Core


Ignore:
Timestamp:
07/09/2023 07:50:52 PM (17 months ago)
Author:
audrasjb
Message:

Docs: Replace multiple single line comments with multi-line comments.

This changeset updates various comments as per WordPress PHP Inline Documentation Standards.
See https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/#5-inline-comments.

Props costdev, audrasjb.
See #58459.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-admin/includes/class-wp-site-health.php

    r56117 r56174  
    773773        }
    774774
    775         // The PHP version is still receiving security fixes, but is lower than
    776         // the expected minimum version that will be required by WordPress in the near future.
     775        /*
     776         * The PHP version is still receiving security fixes, but is lower than
     777         * the expected minimum version that will be required by WordPress in the near future.
     778         */
    777779        if ( $response['is_secure'] && $response['is_lower_than_future_minimum'] ) {
    778780            // The `is_secure` array key name doesn't actually imply this is a secure version of PHP. It only means it receives security updates.
     
    15581560     */
    15591561    public function get_test_https_status() {
    1560         // Enforce fresh HTTPS detection results. This is normally invoked by using cron,
    1561         // but for Site Health it should always rely on the latest results.
     1562        /*
     1563         * Enforce fresh HTTPS detection results. This is normally invoked by using cron,
     1564         * but for Site Health it should always rely on the latest results.
     1565         */
    15621566        wp_update_https_detection_errors();
    15631567
     
    15861590
    15871591        if ( ! wp_is_using_https() ) {
    1588             // If the website is not using HTTPS, provide more information
    1589             // about whether it is supported and how it can be enabled.
     1592            /*
     1593             * If the website is not using HTTPS, provide more information
     1594             * about whether it is supported and how it can be enabled.
     1595             */
    15901596            $result['status'] = 'recommended';
    15911597            $result['label']  = __( 'Your website does not use HTTPS' );
     
    18411847        }
    18421848
    1843         // Run the auto-update tests in a separate class,
    1844         // as there are many considerations to be made.
     1849        /*
     1850         * Run the auto-update tests in a separate class,
     1851         * as there are many considerations to be made.
     1852         */
    18451853        $automatic_updates = new WP_Site_Health_Auto_Updates();
    18461854        $tests             = $automatic_updates->run_tests();
     
    33793387        $headers = array();
    33803388
    3381         // Include basic auth in loopback requests. Note that this will only pass along basic auth when user is
    3382         // initiating the test. If a site requires basic auth, the test will fail when it runs in WP Cron as part of
    3383         // wp_site_health_scheduled_check. This logic is copied from WP_Site_Health::can_perform_loopback().
     3389        /*
     3390         * Include basic auth in loopback requests. Note that this will only pass along basic auth when user is
     3391         * initiating the test. If a site requires basic auth, the test will fail when it runs in WP Cron as part of
     3392         * wp_site_health_scheduled_check. This logic is copied from WP_Site_Health::can_perform_loopback().
     3393         */
    33843394        if ( isset( $_SERVER['PHP_AUTH_USER'] ) && isset( $_SERVER['PHP_AUTH_PW'] ) ) {
    33853395            $headers['Authorization'] = 'Basic ' . base64_encode( wp_unslash( $_SERVER['PHP_AUTH_USER'] ) . ':' . wp_unslash( $_SERVER['PHP_AUTH_PW'] ) );
Note: See TracChangeset for help on using the changeset viewer.