• Howdy,

    I’m trying to create a multisite install for a client who already has a legacy site on their main domain.

    They don’t want to take that site down until the new site is ready, so what I had planned was to stage the new multilingual site in a different web root with domains set up like so:

    en.domain.com
    jp.domain.com
    tw.domain.com
    cn.domain.com

    And when it was all ready to go we’d just point the http://www.domain.com at en.domain.com. It seemed like a sensible approach to me.

    However, now that I’m setting it up I’ve discovered that WordPress wants to use the en.domain.com as the base domain for the other sites in the network, so I’d end up with jp.en.domain.com instead of jp.domain.com.

    This is my first attempt at a multisite install, so I didn’t see this coming at all. Can anyone think of a way around this problem?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    What’s in domain.com?

    Because yes, you need WP installed in domain.com if you want foo.domain.com. You may be able to install in domain.com, set up a static front page that is the same as current domain.com, and then build behind the scenes.

    (Caveat: In WP 3.5 you will be able to install in domain.com/bar/ and then run from domain.com, but that doesn’t help your problem at all)

    Thread Starter infoxicated

    (@infoxicated)

    Thanks for your response, Mika – it’s a shame there isn’t a way around this. I think what I’ll have to do is just stage it in English only then perform a site move operation when it comes time to make it live, then set up the multisite configuration.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    It’s a drawback to any site build out. Moving sites is a pain.

    Generally I build it all local as domain.loc, and then when I’m ready to go live, search/replace the DB for loc/com

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Multisite sub-subdomain issue’ is closed to new replies.