We're in the process of setting up our first multi-site. The primary site is a new domain name and we've got it up and running. The first secondary site is one the client is already using and doesn't want to move until the new site is built. To run our initial multi-site tests, we used a domain name we own but didn't have a use for. So now we've got a sites/correctprimary.com and a sites/wrongsecondary.com. They're sharing a Drupal installation, and we're sharing the users, roles, sequences, etc., but not any of the content. We're using singlesignon to maintain logins for the key users.
My question is whether we can build the entire thing with the substitute domain name, and then rename that directory to the proper secondarydomain.com name, point the proper name at that domain, and expect it to work. If so, is there anything else we need to think about and prepare for as we build? If not, any recommendations for how to handle this situation?
Thanks!
Hall
Comments
Sounds right...
Hall - I really don't know anywhere near enough about this to say with any certainty that I know what you need to do, but it DOES sound to me that you're on the right track with your idea about building it with the substitute name and then just rename it and set it up to work with the new name.
You'll perhaps need to resort to some htaccess chicanery if you haven't already, though this is dependent on your server setup - and now with 5 I'm not really sure just how it handles that - it could be completely different for all I know.
Sorry I wasn't much help!
This is a 4.7 installation
This is a 4.7 installation as we had to start building without knowing when 5 would be released. The original deadline for the launch was yesterday, pushed back by the client now two weeks, but still not time to handle all the issues of a major installation in a new version, I think.... though that multi-domain module sure sounds nice.
As for htaccess chicanery, our host seems pretty well set up for that using cPanel to set up additional domains. The additional domain is working fine.
Thanks for the input. Anyone else? Anyone ever done this this way?
Directory Link
I run a multi-site installation where each new customer gets a subdomain off one of mine, i.e. customer.mydomain.com
I give customers the ability to attach their own primary domain to their website, i.e. custdomain.com
To do this, I do the following
I have not had good luck "moving" sites directories, probably becuase I keep /files inside the customer's customer.mydomain.com directory and those paths are stored in the DB. Thus, I leave the directory as-is and link to it.
Hope this helps.
I moved a 4.7 site about a
I moved a 4.7 site about a month ago, it worked without any hassle. Two things to think about though:
If you're storing your themes and modules in the site directory then it'll cause problems. We were storing our theme in the sites directory, and when the site moved it broke quite a lot. If an admin user remains logged in before moving, they can then go to the themes admin page and reselect the correct theme and it will be fine again. Alternatively, creating a symlink between the old domain and the new one would probably fix it.
Check where you are storing your files directory before starting. If it's in /files then it'll cause a problem when you add multiple sites later. If it's in /sites/yourdomain.com then it'll cause problems when moving. It can be done, but if you can avoid it then do.