[wp-trac] [WordPress Trac] #50100: Native domain mapping does not handle both WWW and non-WWW versions of a domain - both should work
WordPress Trac
noreply at wordpress.org
Mon Jan 23 17:59:08 UTC 2023
#50100: Native domain mapping does not handle both WWW and non-WWW versions of a
domain - both should work
--------------------------------+------------------------------
Reporter: jodamo5 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Networks and Sites | Version: 5.4.1
Severity: normal | Resolution:
Keywords: needs-testing | Focuses: multisite
--------------------------------+------------------------------
Comment (by KZeni):
Replying to [comment:8 siparker]:
> Can someone please look at implementing this into core.
>
> a www or non www domain should not be treated as a separate domain name
in this context. There have been discussions around multiple domain
mapping as well as canonical usage to fix this issue but the usage of the
www subdomain should be treated separately to these queries.
>
>
Agreed. It's putting extra steps into getting a site set up (some being
more technical than what's ideally needed [ex. manually add your own
.htaccess redirect rule via SFTP, or similar.])
Meanwhile, the number of instances where it would make sense for it to
simply resolve both www and non-www to the same multi-site network site
must greatly outweigh the number of sites where they should be kept
separate. So why is it that this is currently catering to that much less
likely scenario?
Getting this implemented will greatly reduce potential oversights (it
might not be set up for people and things aren't working properly for some
of their visitors [them then not able to access the site due to
including/excluding www when it should/shouldn't] without them knowing),
reduce the amount of technical knowledge & steps to be done to get it to
work for the most common scenario when network sites have their own domain
name, etc.
Seems unfortunate that this seemingly stopped seeing discussion & progress
3 years ago when it's still just as relevant today. Is there an update on
where this stands now & what the next steps look like? Were there
discussions that took elsewhere & this ticket just needs to be caught up?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/50100#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list