Is Multi-Domains the best plugin for this use case? or networks for wordpress or another option?

Networks for WordPress is Compatible up to: 3.4-beta4 while Multi-Domains is showing Compatibility with Multisite 3.4.2 (Does this include WP 3.4.2?) and BuddyPress 1.6.1

So Kimberly, if I understand your explanation, if we want to give the ability to use any domain across our network, with different themes on each network and allow the users to pick sub-domains to host their blog network on across the network, Multi-Domains is the best pick?

Continuing this thread in this specific forum, since I could not find how to add the multi-domains tag to https://premium.wpmudev.org/forums/topic/multi-network

  • Timothy
    • Chief Pigeon

    I've not seen any issues with using Multi-domains with the latest version.

    So Kimberly,

    I'm Timberly, I mean Timothy :wink:

    if I understand your explanation, if we want to give the ability to use any domain across our network, with different themes on each network and allow the users to pick sub-domains to host their blog network on across the network, Multi-Domains is the best pick?

    Users can have blogs at any domain name you allow, you can also restrict them.

    You can't separate themes between domains, any themes network activated will be available on all domains.

    So Kimberly, if I understand your explanation, if we want to give the ability to use any domain across our network, with different themes on each network and allow the users to pick sub-domains to host their blog network on across the network, Multi-Domains is the best pick?

    Still Timothy :slight_smile:

    As I mentioned above, you can't restrict the themes to a specific domain.

    Hope this helps.

    Take care.

  • drivencompassion
    • The Incredible Code Injector

    From the domain mapping plugin link

    Significantly this plugin also auto-detects whether your site is a sub-domain or sub-directory install and works just fine for both.

    So that wouldn't work for this use case, although it would work for the individual blog owners within our network who want to point theirdomain.com to theirdomain.network1.com

    In addition to that, the use case needs to support domain mapping for entire networks, not just individual blogs, run under a primary network.

    For example, domain1.com is the primary network domain where all the plugins and multi-domain is installed. In addition, there are other blog networks run via multi-domain under domain2.com and domain3.com, that all have their own sub-domain/sub-directory network of blogs as well. Right now, domain2.com is forwarding to domain1.com, so I am curious what setting or configuration I need to do on these other domains to allow them to use multi-domain plugin to run on domain1.com, while also allowing domain2.com and domain3.com, etc to have their own blog networks, without redirecting the user to domain1.com?

  • Timothy
    • Chief Pigeon

    So that wouldn't work for this use case, although it would work for the individual blog owners within our network who want to point theirdomain.com to theirdomain.network1.com

    It wouldn't?

    Because that's what I'm doing. :slight_smile:

    http://cowpat.net <-- My main sandbox network site

    http://cowpat.org <-- This domain is on Multi-Domains to allow people to have a site on that domain and is also mapped to a blog in the network.

    Multi-domains lets your users get sites at any of your allowed domains.

    Domain Mapping will map those domains to a sub site you create.

    Plugins and themes are shared on the whole network, because Multi-domains isn't a multi-network plugin. It simply allows your users to select which domain they wish their site to be under.

    Hope this clarifies.

    Take care.

  • drivencompassion
    • The Incredible Code Injector

    So you have multi-domains installed on your main site: http://cowpat.net which also allows http://cowpat.org to be managed on the .net as far as plugins, themes, users, etc without redirecting to the .net site or requiring a second install?

    How did you set up multi-domains, so that .org doesn't just redirect to .net as mine does? I'd like to keep those two+ networks running their own set of blogs, wherever the user decides to activate their blog, and not require the blog to just redirect to the primary install.

  • drivencompassion
    • The Incredible Code Injector

    For now, the setting I have is to add & make the additional domains plugins on /wp-admin/network/settings.php?page=multi-domains

    But this alone, only causes the secondary domains to redirect to the primary domain. They don't allow the users to choose the preferred domain on the secondary domain logging/registration screen as you show in your screenshot.

  • drivencompassion
    • The Incredible Code Injector

    Can multi-domain (since it's updated regularly, unlike these others) provide the functionality found in:

    https://wordpress.org/extend/plugins/wp-multi-network/
    https://wordpress.org/extend/plugins/bp-multi-network/
    http://wpebooks.com/networks/
    https://wordpress.org/extend/plugins/networks-for-wordpress/

    If not, why not?

    Still not sure why I can't get multi-domain to load any other domain other than the primary, where the other domains simply just redirect to the primary install.

  • Timothy
    • Chief Pigeon

    Hey again.

    How did you set up multi-domains, so that .org doesn't just redirect to .net as mine does? I'd like to keep those two+ networks running their own set of blogs, wherever the user decides to activate their blog, and not require the blog to just redirect to the primary install.

    Basically I set up multi-domains. This lets you offer blogs on multiple domains.

    It's not like two networks though, in other words if you enable themes and plugins for your network then they are available for all sites. All Multi-domain does is let you offer blogs on different domains.

    I then set up a sub blog on the http://cowpat.net called http://cowpatorg.cowpat.net and used the domain mapping plugin to map in that http://cowpat.org domain.

    Multi-domains is what lets the user choose if they want a blog on http://cowpat.net or http://cowpat.org

    Is this making more sense?

    Take care.

  • Timothy
    • Chief Pigeon

    So what if a user signs up for http://usersblog.cowpat.org? Is the blog actually hosted at http://usersblog.cowpatorg.cowpat.net?

    Nope.

    If they create a site with http://usersblog.cowpat.org then that is the actual url.

    You can also map to those.

    When you add a domain to Multi-Domains, it's not mapping the domain for use. That's why it goes no where. It's making it available for people to create their site on.

    If you want it to go somewhere then you need to map it as described above.

    Take care.

  • Timothy
    • Chief Pigeon

    Is there any reason to use multi-domains without domain mapping plugging

    Yes, if you're not interested in having to maintain two sites for a network, then you don't have to.

    If you do want two sites then you can create two sites with domain mapping.

    You might like to offer:

    domain.co.uk
    domain.eu
    domain.com
    domain.net

    But you might not want to have unique content for them all. It's more admin time.

    Multisites doesn't handle any domain mapping, so it's only needed if you want those domains mapped as well.

    @tom.eagles I own a few :wink:

    I also own http://breakwind.co.uk it's a really old and probably spammed out site now.

    Take care.

  • Timothy
    • Chief Pigeon

    lol should get broken-wind

    then you can proudly say hey i have "broken wind"

    Some of the slogans we came up with was "Break some Wind today!" "Breaking Wind since ....." whenever the domain was purchased I forget.

    It originally went with a retail shop I use to own and run in Yorkshire but that's another story. lol

    Take care.

  • drivencompassion
    • The Incredible Code Injector

    So now that I have network activated domain mapping w/ Pro Sites, when I go to pro sites, my second domain is not listed. But when I go to Add New Site > Site Address >

    There is a drop down after naming the sub-domain, which lists both the primary domain AND my domain2.com

    I am assuming I need to Add New Site, before I can assign it Pro Sites status, before the secondary domain will be allowed multi-domain functionality via domain mapping right? Do I enter * into the sub-domain, and select domain2.com from the drop down?

  • drivencompassion
    • The Incredible Code Injector

    Just tried leaving the subdomain blank when adding a New Site, so I can assign it to Pro Sites > domain map > multi domain to hopefully function. The result of leaving the sub-domain blank in adding a New Site for domain2.com via domain1.com/wp-admin/network/site-new.php is:

    Missing or invalid site address.

  • drivencompassion
    • The Incredible Code Injector

    As suggested, I created a site like normal by adding a site, ie. domain2.domain1.com to domain1.com

    I gave it permanent Pro Site status.

    Now, where do I map the domain? Under "Domain mapping Options" there are no options to map anything other than entering the dedicated IP that is shared between both domain1.com and domain2.com

    Do I change the Site URL under domain1.com/wp-admin/network/site-info.php settings from domain2.domain1.com to just domain2.com here? Or is there another area where domain mapping takes place?

  • drivencompassion
    • The Incredible Code Injector

    So when you say go to Admin --> Tools --> Domain Mapping

    That's available to each site.

    When I go to domain2.domain1.com, On Firefox, Safari and Chrome I get:
    Server not found

    Firefox can't find the server at domain2.domain1.com.

    Check the address for typing errors such as
    ww.example.com instead of
    http://www.example.com
    If you are unable to load any pages, check your computer's network
    connection.
    If your computer or network is protected by a firewall or proxy, make sure
    that Firefox is permitted to access the Web.

  • Timothy
    • Chief Pigeon

    Server not found

    Firefox can't find the server at domain2.domain1.com.

    Sounds like the wildcard is not setup correctly.

    Both domains in Multisite Domains need to have a wildcard set, that's need so *.domain.com aka anything.domain.com will work.

    Are they not? Your last post implies they are?

    Thanks.

  • Timothy
    • Chief Pigeon

    nd still nothing there other than a blank index / cgi-bin

    If you're getting a blank index/cgi-bin that would imply that the IP/A record is still not correct on that domain.

    The reason I say this is because when you're not mapping anything.domain.com i.e. anything as the sub domain and the domain itself should just load your WordPress site.

    Because it doesn't it means the domain/wc is hitting a different directory, in other words it's not hitting WordPress so WordPress couldn't do anything with it.

    After submitting Action: Add... No Result: There is no confirmation, or listed result of domain.

    Is the newly added domain name not there where the field is once you add?

    Take care.

  • drivencompassion
    • The Incredible Code Injector

    I think domain2 not hitting wordpress on domain1 because (in response to your last question) the newly added domain name is NOT where the blank text field was once I click Add action. It just refreshes to the same screen with a blank text field under Custom Domain.

  • drivencompassion
    • The Incredible Code Injector

    A new issue for others following along to check, even if you have assigned the same IP to both domains. If you are using WHM/Cpanel, go to list accounts under Account Information. Find your domain, and ensure the IP there is the same as what you edited to DNS zones in each domain to.

  • drivencompassion
    • The Incredible Code Injector

    Tried waiting this out, restarting my computer, as well as dscacheutil -flushcache ... but still getting this now on domain2.com:

    If you are the web site owner, it is possible you have reached this page because:

    The IP address has changed.
    There has been a server misconfiguration.
    The site may have been moved to a different server.

    If you are the owner of this website and were not expecting to see this page, please contact your hosting provider.

  • Timothy
    • Chief Pigeon

    It sounds to me like things are getting more messed up with the DNS there.

    Just say to your host:

    I'm running WordPress multisite.

    I need both these domains:

    LIST DOMAINS

    To point to my WordPress website, they must use my dedicated IP.

    I need my dedicated IP to also point to my WordPress website.

    I then need a wild card for both domains, also pointing to that dedicated IP.

    It should all then just work.

    Let me know what they say.

  • drivencompassion
    • The Incredible Code Injector

    Had a lot of back and forth with my datacenter including some of the following:

    Still getting the same error when going to domain2.com:

    If you are the web site owner, it is possible you have reached this page because:

    The IP address has changed.
    There has been a server misconfiguration.
    The site may have been moved to a different server.

    If you are the owner of this website and were not expecting to see this page, please contact your hosting provider.

    YES, I TRIED dscacheutil -flushcache

    This is my setup as far as I'm aware, FYI... I'm running WordPress multisite.

    I need both these domains:

    domain1.com
    domain2.com

    To point to my WordPress website, they must use my dedicated IP

    I need my dedicated IP to also point to my WordPress website.

    I then need a wild card for both domains, also pointing to that dedicated IP.

    It should all then just work.

    It looks like the problem may not be your local cache or the server, but rather your ISP's DNS cache. I get the correct IP address when I ping, So we know the DNS is configured correctly on your server. To eliminate your local ISP DNS, try changing your local resovlers from whatever they are now to something else, such as Google's 8.8.8.8

  • drivencompassion
    • The Incredible Code Injector

    This morning, going to domain2.com gives me a root page

    Index of /

    cgi-bin/

    Instead of a wordpress install, hoping this is better news than the other page I was getting, but still don't know what I should ask you or my datacenter for as my next steps? Any ideas?

  • Timothy
    • Chief Pigeon

    It can't be correct if you still see the root page.

    Or if it is on the server then you might need a restart for it to take affect/refresh

    If it were working on the server level then the IP would resolve to your website.

    Did your host not look into this again to ensure the IP resolves direct to the WordPress install?

    Thanks.

  • drivencompassion
    • The Incredible Code Injector

    Just sent my email response, but have another related followup question that might help the public.

    I originally installed wordpress on domain1.com's DocumentRoot … is that not the right place? Does it need to be on the IP itself, even though domain1.com is on the dedicated IP ... ie. xx.xx.xx.xx/~domain1

  • drivencompassion
    • The Incredible Code Injector

    After I reminded my datacenter that the wordpress install is currently on http://xx.xx.xx.xx/~domain1 instead of http://xx.xx.xx.xx/ directly on the DocumentRoot for that IP, they replied with:

    Loading the temporary URL xx.xx.xx.xx/~domain1 currently redirected the site to http://domain1/protected/ and loads without issue. The reason that the IP alone will not work is that it is not assigned as a dedicated IP but rather as Main/shared IP for mybeat. The redirect is being triggered by your .htaccess file. If you would like to access the site via just the IP then the domain would need to be assigned a Dedicated IP.

    My latest query/reply:

    If I assign domain1 to a dedicated IP instead of a Main/Shared IP as it is now, how do I assign the secondary sites like domain2.com to the same IP to use?

  • Timothy
    • Chief Pigeon

    I originally installed wordpress on domain1.com's DocumentRoot … is that not the right place? Does it need to be on the IP itself, even though domain1.com is on the dedicated IP ... ie. xx.xx.xx.xx/~domain1

    That's fine. It's not installed with the domain name.

    Loading the temporary URL xx.xx.xx.xx/~domain1 currently redirected the site to http://domain1/protected/ and loads without issue. The reason that the IP alone will not work is that it is not assigned as a dedicated IP but rather as Main/shared IP for mybeat. The redirect is being triggered by your .htaccess file. If you would like to access the site via just the IP then the domain would need to be assigned a Dedicated IP.

    Ya, as I said in email and in this thread... The issue has always been because of where the IP goes.

    When you enter the IP along you should see your site.

    If I assign domain1 to a dedicated IP instead of a Main/Shared IP as it is now, how do I assign the secondary sites like domain2.com to the same IP to use?

    You can add it, but all secondary domain names don't need to be assigned to the IP as such, you just edit the A Record to use that IP. Or an addon domain.

    Take care.

  • drivencompassion
    • The Incredible Code Injector

    I'm switching from a Main/Shared IP to dedicated IP and going for the Addon Domains method then, instead of creating domains with their own accounts in WHM/cpanel. Since it looks like that's what is causing the problem, since as soon as you create a new domain account and allow it to use the same IP as the dedicated IP in domain1.com, the IP switches automatically from a Dedicated IP to a Main/shared IP.

  • drivencompassion
    • The Incredible Code Injector

    Can someone confirm, for this step:

    2. In the Document Root field, enter the directory that will contain the addon domain’s files.

    If we install in the root directory of domain1.com, do we enter a blank Document Root? OR do we enter the sub-domain / username we created as a prosite, and have to create a directory with the same name both for every multi-domain/addon domain?

  • drivencompassion
    • The Incredible Code Injector

    Since i didn't hear back, I went ahead and removed the secondary domain from WHM, and instead added it using the addon domains suggestion above. I am testing the username created for the prosite but as of now, the secondary domain doesn't work at all yet.

    In cpanel, where I set up the secondary domain as an addon domain, there is an option for redirection, but I have it set up for "not redirected" - as I want the traffic to stay within domain2.com

    I will post again, if domain2.com is still not loading after giving DNS some time to propagate.

  • Timothy
    • Chief Pigeon

    To answer your question, you enter the DocuementRoot.

    So if that was something like /home/username/public_html then that is the root for that domain so it needs to be set as such.

    If you use an addon domain, the path must still go to your actual install.

    Thanks.

  • drivencompassion
    • The Incredible Code Injector

    I entered /home/usernameofDomain1/public_html as you suggested.

    Before making that change, I had /public_html/Domain2UserName

    We'll see if this propagates correctly :slight_smile:

    NOTE: When updating document root in CPanel, there's a Picture of a Home, followed by a "/" and then a text box to enter the document root. Maybe that implies i/we should remove the first "/home/" from /home/usernameofDomain1/public_html as you suggested?

  • drivencompassion
    • The Incredible Code Injector

    Looking back at it, looks like since this was altered within Domain1's Cpanel, Addon Domains detected /home/usernameofDomain1/ and left behind just public_html

    Should it be redirecting to Domain1.com/wp-signup.php?new=www.domain2.com ?? That's what it's now doing.

    NOTE: For some reason (I didn't put this there) there's a "/\..*$" under "Redirects to" in Domain1's Addon Domain's / Cpanel.

  • Timothy
    • Chief Pigeon

    Hey

    So if that was something like /home/username/public_html then that is the root for that domain so it needs to be set as such.

    That was an example based on the path, so with an addon domain you see "Document Root" as in the path is there. So it's from that, in many hosting environments that can be /public_html/ as you have.

    I logged in with those details you gave me.

    See http://domain.com/ now. It should be mapped to a site.

    The issue was the path when I looked.

    Thanks.

  • drivencompassion
    • The Incredible Code Injector

    Glad to see Domain2.com load it's own site, instead of forwarding to Domain1.com/wp-signup.php?new=www.domain2.com as I saw last...

    Did you make any changes when you logged in? Just so I know when I add additional domains to the mix to test, I just need to point them all to public_html?

  • drivencompassion
    • The Incredible Code Injector

    I dont see any toolbars for Admin --> Tools --> Domain mapping

    What I do see after logging into the Network Admin Dashboard, is under the Settings menu... there is Domain Mapping.

    But that's just options to set the dedicated IP.

    Can you point me in the right direction, as you may be talking about an Admin panel somewhere else?

  • drivencompassion
    • The Incredible Code Injector

    I was originally looking at Domain1.com/wp-admin/network/

    My Sites > Network Admin > Dashboard, where there is no Tools menu, just a Settings > Domain Mapping

    For anyone else looking for the location Timothy helpfully pointed out, it's under domain1.com/wp-admin/
    Tools > Domain mapping

    @Timothy, I don't see domain2 listed here. Even though it seems to work, is it ok that domain2/Any domains for that matter is not listed here under Tools > Domain mapping?

  • drivencompassion
    • The Incredible Code Injector

    When I hover over "My Sites" when logged in as superadmin, I see domain2 as an option. I go to that dashboard, which is domain1.com/domain2/wp-admin/ ... and that just shows:

    Permission Denied
    Not Found / No Access

    The page you are looking for either does not exist, or you do not have the permissions to access it.

    FYI: The super admin user is assigned to both domain1 and domain1.com/domain2

    Any idea where these permission settings need to be updated, to see where you updated the domain mapping on domain2?

  • drivencompassion
    • The Incredible Code Injector

    Thanks again Timothy!

    One more related issue: In the "My Sites" drop down, if I hover over Domain2 and click on dashboard, where can I get WP to recognize it's a subdomain? It's currently taking it to subdirectory. I have checked in settings, but can't find where all the locations I need to edit are to ensure when I click around, the links take me to the subdomains and not sub directories which don't work?

  • PC
    • WPMU DEV Initiate

    Hiya,

    Greetings of the day.

    I was doing a regular followup today and found that we missed your last post on this one.

    Are you still seeking support on this one or managed to get it resolved ? Please let us know so that we can take it further and assist you on the same :slight_smile:

    Thanks for being a great community member !

    Cheers
    PC

  • Timothy
    • Chief Pigeon

    Hey again, not sure how I missed your last post.

    Apologies about that.

    One more related issue: In the "My Sites" drop down, if I hover over Domain2 and click on dashboard, where can I get WP to recognize it's a subdomain? It's currently taking it to subdirectory. I have checked in settings, but can't find where all the locations I need to edit are to ensure when I click around, the links take me to the subdomains and not sub directories which don't work?

    A lots gone on in this thread now, so I had a quick read but wasn't sure what was going on there. I looked up our past email and logged in to fix the problem for you.

    It should now be working fine.

    As there was another site of the same name I had to append a 1 on there to make it unique. You can see this in:

    Admin --> Network --> Sites

    Take care.

  • drivencompassion
    • The Incredible Code Injector

    Now when I go to sites, the site with a 1 at the end is listed and correctly goes to the subdomain when I go to the dashboard. The previous site without the 1 is not listed as an option in the site dropdown anymore.

    Figured I'd delete the non 1 appended site, and rename the one you created without the one, but had a few questions first before I do that and test adding new sites to the mix.

    The site with the appended 1 isn't a pro site like the other site; and isn't domain mapped or have multi-domains configured for it, right? Does all these need to be tested first?

  • Timothy
    • Chief Pigeon

    The previous site without the 1 is not listed as an option in the site dropdown anymore.

    Adding yourself as a site admin on that blog should add it do your drop down.

    The site with the appended 1 isn't a pro site like the other site; and isn't domain mapped or have multi-domains configured for it, right? Does all these need to be tested first?

    Is there a difference between the two?

    If the one without the 1 is more developed why not keep that one?

    I mean if it already has mapping, contant, etc, is there a need to use the other one?

    Take care.

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.