[wp-trac] [WordPress Trac] #36507: Invalid URLs in network admin when WP Core is in custom subdirectory

[WordPress Trac]

#36507: Invalid URLs in network admin when WP Core is in custom subdirectory
--------------------------------+------------------------------
 Reporter:  flixos90            |       Owner:
     Type:  defect (bug)        |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  Networks and Sites  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  has-patch           |     Focuses:  multisite
--------------------------------+------------------------------

Comment (by flixos90):

 Replying to [comment:5 DrewAPicture]:
 > To be fair, while WordPress is defensively coded in most places, we
 should never assume that because something doesn't throw errors that it's
 supported functionality by default. If it's working as ''designed'', we
 should have corresponding documentation.

 That makes sense, thanks for clarifying. In this case though, I would like
 to propose actually adding support for this. WordPress supports this
 behavior on non-multisite setups (using `home` and `siteurl` options) and
 I think it would be straightforward to support that behavior on multisite
 as well - basically let's think about this as an enhancement (which would
 go beyond this ticket)! :)

 I would gladly dig into this to find a solution. Maybe we can talk about
 this in the next multisite chat. #27287 is another ticket related to this
 issue. The main problem seems to be that in a multisite (especially in
 network context) only the domain and path of a site are honored while
 their individual settings `home` and `siteurl` are ignored. I would expect
 that domain and path of a site are similar to its `home` option - however
 it's `siteurl` option is not considered in these areas. That doesn't
 matter for a default setup, but it causes problems with a custom directory
 structure.

 Another problem that results from this lack of parity is the scheme of the
 URL. While `home` and `siteurl` are full URLs with http or https in front
 of them, this setting is not available from domain and path of a site in a
 multisite. While WordPress detects this scheme on a regular site and
 redirects, it doesn't do that on a multisite (when some sites are HTTPS
 and others aren't).

 I think we would need to determine these issues more precisely and where
 they appear before starting to think about eventual fixes. But I think
 it's worth to tackle this.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/36507#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform