• Firstly, what’s the purpose of using the www subdomain?? I understand it has to do with cookies, but with regard to WordPress – should I care?

    Now, I currently have a network of sites — each domain forwarded — and they won’t work with www. So, to avoid errors when visitors mistakenly visit https://www.subsite1.com rather than subsite1.com, I’ve setup a subdomain forward DNS record. This solves the problem MOST of the time; however, this won’t redirect something like https://www.subsite1.com/my-blog-post/. Am I doing it wrong? Would it be better to code it into the htaccess?

    RewriteCond %{HTTP_HOST} ^www\.subsite1\.com [NC]
    RewriteRule ^(.*)$ https://subsite1.com/$1 [L,R=301]
Viewing 3 replies - 1 through 3 (of 3 total)
  • Firstly, what’s the purpose of using the www subdomain??

    None.

    Other than legacy / nostalgic reasons.

    I understand it has to do with cookies, but with regard to WordPress – should I care?

    Nope.

    A long time ago when I used Multisite (or was it WPMU?) with the MU Domain Mapping plugin, I simply pointed both the www- and non-www domains to the same blog, selected one of these as the PRIMARY/CANONICAL domain (I don’t remember what it was called), and it worked flawlessly — all links from one automatically forwarded to the same links on the other. No code involved.

    Thread Starter Kyle Scheuerlein

    (@kylesureline)

    Hm. I’ve known about that plugin but was trying to do without since domain mapping is part of the core WP now. Maybe I’ll ask their support about this.

    Thread Starter Kyle Scheuerlein

    (@kylesureline)

    It seems that many threads across the web are encouraging mapping domains without the plugin since it is now a native feature. (see here)

    So, since I’m bumping this thread, let me rephrase the problem.

    No matter what I try, I cannot get https://www.subsite1.com to work. What am I doing wrong?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Subsites won’t run on www…?’ is closed to new replies.