WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

#39786 closed defect (bug) (duplicate)

Multisite: Site Address (URL) does not reflect proper https protocol on fresh install

Reported by: jrmorris77 Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Networks and Sites Keywords:
Focuses: multisite Cc:

Description

Description of issue:
When doing a fresh install of WordPress 4.7.2 using https:// as the protocol throughout the entire process, when enabling multisite Siteurl and Home URL are correctly registered as https:// but Site Address (URL) stays http://. After checking the DB, no references are in the database other than the default post content and default comment author URL. All options and meta values reference the correct schema.

Line 161: /wp-admin/network/site-info.php

<?php
                // The main site of the network should not be updated on this page.
                if ( $is_main_site ) : ?>
                <tr class="form-field">
                        <th scope="row"><?php _e( 'Site Address (URL)' ); ?></th>
                        <td><?php echo esc_url( $details->domain . $details->path ); ?></td>
                </tr>
                <?php
                // For any other site, the scheme, domain, and path can all be changed.
                else : ?>
                <tr class="form-field form-required">
                        <th scope="row"><?php _e( 'Site Address (URL)' ); ?></th>
                        <td><input name="blog[url]" type="text" id="url" value="<?php echo $parsed_scheme . '://' . esc_attr( $details->domain ) . esc_attr( $details->path ); ?>" /></td>
                </tr>
                <?php endif; ?>

Change History (1)

#1 @flixos90
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed
  • Version 4.7.2 deleted

Hi @jrmorris77, and welcome to Trac!

Thanks for the report. This issue was already described in #39365, and fixed in [39930], so it will be fixed in the next major release. However it is only a display issue. For the main site, the code snippet you posted always displays the URL with http:// regardless of what is actually specified in the database. So the actual values of URLs should be correct, they are just displayed incorrectly in this one location.

Note: See TracTickets for help on using tickets.