Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter fwdcar

    (@fwdcar)

    sorry – typo in my post. Should of had an equal sign like this:
    For example: Network 1 – site1=abc.com and site2=xyz.com.

    This should be possible, but it is a little clunky.

    If you create a site within the network you want it in, give it a bogus subdomain/folder when you create it. After creation, immediately edit that site, and you will see you can change the url to anything you want, including another domain. WordPress will make it just work.

    Notice I said Site, not Network.

    Thread Starter fwdcar

    (@fwdcar)

    Thanks for the reply NDx. The adding, then editing of the site to new URL sure seemed to work as planned, but going either to the site or the dashboard produces an error:

    “Error establishing a database connection”
    …..
    “Could not find site zzzzzzzzzz. Searched for table wp_blogs in database zzzzzzzz. Is that right?”
    (…..And yes this was all right)

    Looking in wp_blogs, the new site is there (blog ID 18), and all 10 tables for a site are there (for example: wp_18_options, etc.).

    All my other sites, including some in that same network, work just fine, so I know it’s not a ‘true’ DB connection issue.

    I’ll keep poking around…it must be something simple and right under my nose here.

    any ideas?
    Thanks again….

    did you make this work? looking for exactly the same setup…

    Thread Starter fwdcar

    (@fwdcar)

    no tinus I did not. I concluded that since i was using the multi-network plugin, it wanted to use the siteID (which is really the network id) from the table wp_blogs, in the internal url rewriting process. So, it seems that if one needs a site with its own domain name (not a sub-domain or sub-directory) than it has to be a new network. Add a new network, give it the domain name and it automatically creates its first site within that network with that domain name.

    Hope this helps

    Yeah, that does help – if that’s the case then this is really a deal breaker – what else would one want a network for?

    Too bad that tagging of the authors doesn’t work so that they could chime in and clarify.

    Thread Starter fwdcar

    (@fwdcar)

    I was hoping they would too because I always felt I was just missing something, and something simple at that.

    I read elsewhere that the addition of another plugin – MU domain mapping – would possibly allow this, however when I looked into it, it hadn’t been updated in a while and was only compatible with WP up to 4.0.

    As far as a deal breaker for the plugin, it’s still providing the ability to cleanly have a single codebase and single DB for multiple primary domains, it’s just that separate primary domains need to be in their own network. I can live with that for the benefits I get.

    in my case i am looking for this setup:

    main.tld
    main.tld/network1 (network1.tld)
    main.tld/network1/site1 (site1.tld)

    let’s see, maybe someone responds or i miraculously get it to work…

    I got it to work, but I think it is a DNS and webserver config problem also.

    I got al our domains directed to one main domain (directory). I think it is a Apache Serveralias configuration, I do not know, as it is a cpanel configuration I got on Loopia server provider.

    I just went through the steps (also described here above):
    1. Made a new website
    2. Changed to the domain (root)
    3. Moved it to main Network
    4. Set a site as start page
    5. Reloaded the Network.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Multiple Domains within a Network’ is closed to new replies.