[wp-trac] [WordPress Trac] #52248: Multisite new site default protocol
WordPress Trac
noreply at wordpress.org
Thu Jan 7 18:28:58 UTC 2021
#52248: Multisite new site default protocol
-------------------------------------------------+-------------------------
Reporter: kpetrilli | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting
| Review
Component: Networks and Sites | Version: 5.6
Severity: normal | Keywords:
Focuses: administration, multisite, rest-api |
-------------------------------------------------+-------------------------
Newly created sites in a multisite installation default to HTTP even
though the main site is HTTPS.
== Reproducible by doing the following:
* Installing WordPress, served by nginx;
* First (main) site initially set to use HTTP only
* Enable multisite (subdomain)
* Migrate everything (wp-config.php, database entries) to HTTPS only
* Create a new site
== Expected behavior:
New sites should be created with HTTPS instead of HTTP.
== Issues
When served by nginx, with 80 to 443 redirection (301 Moved permanently),
page editor will not work, while dashboard will, on the newly created
site. The redirection for the API will not work, reporting "offline" error
when trying to save.
== Workaround:
After the creation of the website:
1. Manually change the site's URL to use HTTPS;
2. Manually change all database entries containing `http://` into
`https://` with a plugin such as better search replace.
== Notes
I could not find how to set WordPress' default multisite protocol for new
websites. I would happily avoid installing new plugins for that only.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52248>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list