WordPress.org

Ready to get started?Download WordPress

Forums

Two Dashboards for Each Blog (34 posts)

  1. 785mack
    Member
    Posted 2 years ago #

      Background

    Created a domain based network (sub-domain install) on an add-on domain to the mainsite. Set up a wildcard DNS record and (according to other instructions ) made sure the other domains to be added were parked and NOT redirected. All of that really seemed to have worked -- you could access the Dashboard for each site but when you went to visit the site it would resolve to homepage of the mainsite.

    Contacted Hostgator and they said that couldn't be done. The network setup needed to be path-based and the other domains needed to be changed from Parked to Add-Ons. That Tech person said he was able to make changes to prevent having to do a reinstall. All I had to do was make the changes to the domains, wait for them to propagate and set the network up again.

    Did that. Was instructed to install WP on each of the domains. Did that -although in my understanding that defeats the purpose of MU. But I'm not sure and so I would like to confirm if this is how it should operate:

    * Login as Network Adminstrator, see all the sites (there are just 4 total)
    * Domain mapping is available in tools
    * Can visit each site
    * Can visit each Dashboard
    * Can create pages/posts but nothing changes

    * Log into a site (non superadmin)
    * It's a different dashboard -- it's asking me to update to the latest WP
    * This dashboard is the one I can edit pages/posts and it publishes the changes
    * No domain mapping tool
    * None of the themes, or other plugins I've added to the network are available

    If this is how it's supposed to work -- installing WP for each domain, installing themes and plugins for each domain what is the multiuser advantage?

  2. Are all the domains you are using subdomains of a single root domain?

    I.E. your domain is supernetwork.com, and your subdomains are

    • site1.supernetwork.com
    • site2.supernetwork.com
    • site3.supernetwork.com
    • and so on...
  3. 785mack
    Member
    Posted 2 years ago #

    I think that they are BUT it's the wrong domain.

    The main domain was set up first in it's own WP install:

    maindomain.com

    A few more domain names were purchased and it was decided to go the MU route w/WP. Since maindomain.com is an ecommerce site and we didn't want to mess around with it we left it as a single install. Hostgator said that yes we could set up WP MU using an addonsite*. So supernetwork.com was created. And the Wildcard DNS created on that.

    The subdomains appear as:

    • site1.maindomain.com
    • site2.maindomain.com
    • etc.

    instead of

    • site1.supernetwork.com
    • site2.supernetwork.com
    • etc.

    * I've lost track of addons v subdomains!

  4. So they're two separate domains (mainsite.com and supernetwork.com) and you are trying to run them both together under a single WordPress Multisite account?

    I'm afraid it can't be done. In order to Multisite to function properly, sthe subdomains must be under the same root domain that WordPress is on. I.E., if WP Multisite is on mainsite.com, the subdomains must also be from mainsite.com. You can't mix and match. So site1.supernetwork.com can't be run under the WP Multisite installation on mainsite.com and will need to be run on it's own separate WordPress installation.

    See what I mean?

  5. 785mack
    Member
    Posted 2 years ago #

    Yes and no.

    Mainsite.com is a stand alone site running WP. Not part of the network nor intended to work with supernetwork.com. Supernetwork.com has it's own installation of WP. This was was the site that MU was created.

    As I'm looking at CPanel and the SubDomain section I hope I'm having an "aha" momement that fixes everything! I now see I can create subdomains for supernetwork.com. So if set up the subdomains using supernetwork.com and remove all the ones for mainsite.com will it all magically work?

  6. I don't believe in magic, but it's possible I suppose. For sure, the main (root) installation of wordpress and the subdomains must be related. Not sure what you've done to this point to try and get outside domains to work, so I'm not sure what you have to *undo* first before it all works as it should. :)

  7. 785mack
    Member
    Posted 2 years ago #

    I was able to create site1.supernetwork subdomain but not delete site1.mainsite.com subdomain without deleting the addon domain site1. Reluctant to do that becuase I do not know the consequences.

    The outside domains work in the sense that you can go to the sites. You can see that WP is installed but they are individual installs and appear completely disconnected to the network. But they are on the network as well.

    Anyway -- I appreciate your help....think it's time to throw in the towel on this one and not bother with the MU.

    Thanks.

  8. Well there are definitely advantages to using multisite, but I'll admit it's not for everyone since it's a little more confusing to use.

    I wouldn't give up just yet though... find a domain that isn't critical (or that you've backed up) so you can experiment on it, and give it a shot.

  9. 785mack
    Member
    Posted 2 years ago #

    I may give it another go. Since these are going to very small, static sites I thought it was a good opportunity to try this out....that will be a decision for tomorrow! I've had more thanough of this for today!:-)

  10. Did that. Was instructed to install WP on each of the domains.

    They totally led you down the wrong garden path, unfortunately.

    The outside domains work in the sense that you can go to the sites. You can see that WP is installed but they are individual installs and appear completely disconnected to the network. But they are on the network as well.

    No, they are still not part of the network. I'm sorry to hear your host toally screwed you over on this.

    The usual method is as follows:

    - install multisite on whatever domain you like (also note is it NOT called WPMU any longer. this refers to the old codebase and causes confusion).

    - you can use subdomains or subfolder, which does not matter much if you eventually want to map domains. If the multisite install is an add-on domain, your host has to let you use wildcard subdomains on that. Most do not.

    - you do not install any other instances of WorPress. You go to network admin -> Sites -> Add new. Make a test site.

    - install the domain mapping plugin. Map the domain. On the server side you *park* the domain you want to map on top of your multisite install.

    The tricky bit here is if you have an existing domain you are using, you need to import all the content to your test site first, then move the dns.

    In my experience, most hosts - unless they are WordPRess-specific - know absolutely nothing about multisite and the ones that do manage to screw it up with misunderstanding. They definitely do NOT understand domain mapping.

  11. 785mack
    Member
    Posted 2 years ago #

    Thank you! That was my original set-up: parked domains, mapping them and it was ALMOST working. The index page was not resolving correctly and I was fairly certain it was a MINOR issue. I was just having no luck determining what it was and called Hostgator Tech support. Despite how helpful they were/are it was dowhnill from there. Having to install WP on each domain never made sense to me!

    The wildcard domain is set up. I don't know how, or even if it's possible, to go back to the subdomain insall. They changed to the path based one. I guess that would also mean removing all the subdomains/addon domains for supernetwork.com and parking them (like they were originally).

    BTW, I think where I ran into a glitch is in the network setup settings. In addition to referencing an IP address (or instead of) I should include the domain name - supernetwork.com - so the new sites are attached to that and not maindoman.com.

  12. In addition to referencing an IP address (or instead of) I should include the domain name - supernetwork.com -

    Yes, most definitely.

    IS there any way you can tear it down and re-do it?

    I don't know how, or even if it's possible, to go back to the subdomain insall. They changed to the path based one.

    you mean to go from a subfolder install to a subdomain one? yeah, you can do it.

  13. 785mack
    Member
    Posted 2 years ago #

    ok...I would appreciate knowing if these are the steps I need to take:

    1. Remove the WP install from Sites 1-2-3
    2. Remove Sites 1-2-3 from Supernetwork.com
    3. Remove Sites 1-2-3 as addon/sub-domains
    4. Park Sites 1-2-3
    5. Change wp-config to define( 'SUBDOMAIN_INSTALL', true );
    6. (would that be the only line that needs to change? are there changes to the htaccess)

    7. In Domain Mapping Configuration add supernetwork.com to Server CNAME
    8. Add Sites 1-2-3 to Network
    9. Am I missing anything? Thank you!

  14. before you map domains, make a TEST SITE in the network. Calls it test. make sure it works. Report back here eithe rway before you map domains.

    Change wp-config to define( 'SUBDOMAIN_INSTALL', true );
    (would that be the only line that needs to change? are there changes to the htaccess)

    there's no reason to change formats. and yes you'd ned new htaccess rules.

  15. 785mack
    Member
    Posted 2 years ago #

    Ok, added site called TEST.

    Its address is supernetwork.com/test.

    Can get to it fine, added a post and can see it.

    A theme that I added to the network was available, activated it and it worked. :-)

    And the Domain Mapping tool is available.

    (I'm feeling encouraged here!)

    To be clear, in the current network setting the subdomain install line is set to FALSE

  16. Yes, Subdomain set false makes subfolders (supernetwork.com/test).

    Set true and you get test.supernetwork.com ;)

  17. 785mack
    Member
    Posted 2 years ago #

    Okaaayyyyy .... so, since I'm trying to get back to how I originally set it up do I make that change and do the other steps I outlined up above? Thanks for your help!

  18. Like Andrea mentioned, you don't HAVE to change to subdomains. If you're just mapping them in the end, it doesn't matter.

  19. 785mack
    Member
    Posted 2 years ago #

    That makes sense to me....where I'm not getting a click is how to correct my current set up so that I only have the 1 install of WP, plugins, themes.

    Should I go ahead an unistall WP for those 3 sites? Then remove them from the network? Should I change them back to parked sites and then add them to the network? Or leave them as addons?

  20. Where are your sites now?

    I'm confused if they're already in a network, or if they're all stand-alones.

  21. 785mack
    Member
    Posted 2 years ago #

    You're confused -- imagine how I feel! :-)

    I believe what is going on now is both: network + stand alone.

    Hostgator said that I could set up a WP multisite network on an an add-on domain. Setup the addon domain (supernetwork.com). Activated WPMS with subdomain install. Had 3 Parked domain names. Added sites, used the Domain Mapping plugin, all seemed good except for the index pages for each site were going to maindomain.com.

    After trying a number of things on my own to resolve this - without success - I called HG tech support. Now I'm told no you can't do that you have to create addon domains, change it to path based, etc.

    (Based on this ongoing exercise I think my only problem with the original set-up was not putting supernetwork.com in the CNAME field.)

    Anyway they corrected it on their end and said NOW everything was working right. I added the sites back in, could (can) see them on the network but they didn't seem to be affected by anything done at the network level: themes, plugins, etc.

    Another call to HG and now I'm told I have to install WP on each of the sites I want in the network. When I said that that seemed to defeat the purpose of WPMS I was essentially told that's just the way it is.

    And that's pretty much where we are. If I access Sites 1-2-3 via the network I really can't do anything. If I log into them individually I can and those changes can be published. Which makes sense (at least to me) because those are the indivdiual installs of WP.

    What's the best way to get rid of those stand alone sites (1-2-3)?

  22. 785mack
    Member
    Posted 2 years ago #

  23. http://sellmyfurcoat.com is Multisite, so what you should do is make SUB sites off that:

    http://sellmyfurcoat.com/repair
    http://sellmyfurcoat.com/clean
    http://sellmyfurcoat.com/store

    Then IMPORT all the posts from the related SEPARATE sites into your multisite. Make sure they work.

    Then, and only then, would you install your domain mapping plugin and park the domains on http://sellmyfurcoat.com

  24. 785mack
    Member
    Posted 2 years ago #

    nothing to import. these were not live sites -- only had the domain names. thought this was the perfect opportunity set up a Multisite.

    so do I:

    Remove them as addon sites (and their WP installations)
    Park them
    Uninstall the domain mappling plugin
    Set them up on the network
    Install the mapping plugin
    Map them

  25. nothing to import. these were not live sites -- only had the domain names. thought this was the perfect opportunity set up a Multisite.

    Awesome :) Yes.

    1) Remove their separate WP instance, remove add-ons.
    2) Set them up on the network
    3) Install mapping plugin (or if you have it installed, just let it sit)
    4) Park domains
    5) Plugin-map the domains
    6) Beer

  26. 785mack
    Member
    Posted 2 years ago #

    OMG -- can I start with the Beer first!!

    ok -- hopefully this is the final question/confirmation before I this:

    Remove them from the current network too?

    THANK YOU!!

  27. Remove them from the current network too?

    NO!

    If you already have them ON the network, just set them up as is. Make sure

    http://sellmyfurcoat.com/repair
    http://sellmyfurcoat.com/clean
    http://sellmyfurcoat.com/store

    (or whatever you call them) look right in every way except the domain name.

  28. 785mack
    Member
    Posted 2 years ago #

    Alrighty -- I'm going in....

  29. 785mack
    Member
    Posted 2 years ago #

    First breath of air...

    everything's deleted, parked,etc. I did have to remove the sites from the network and add them back in to have them work correctly. mapped http://sellmyfurcoat.com/store to storemycoat.com. click on visit site and it takes me to maindomian.com -- where I was last week.

    there is a CNAME record for sellmyfurcoat.com.

    a wildcard DNS is set up for sellmyfurcoat.com

    what else should I look for in any of the setups?

  30. 785mack
    Member
    Posted 2 years ago #

    just added an ANAME for sellmyfurcoat.com pointing to the right IP address. there is also one for localhost.sellmyfurcoat.com resolving to 127.0.0.1 -- should i delete that?

    and there is a *.sellmyfurcoat.com A record

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.