Greetings, after days of trying to set up my site I decided to start over with a new hosting service. Installation went 100% better with the new host. Now would like to set up a multi-site configuration. I have been reading some of the posts and have gained some valuable information but I am still confused about how to set it up
I have my domain example.com, and two sub domains example1.example.com and example2.example.com. I have redirected the subdomains to http://example1 and http://example2
The main domain will be a photo gallery like shutterfly; the subdomains will be e commerce type sites with shopping carts
Is a single install, single database the best way to proceed?
Are there modules designed for this type of set up?
I know you all have heard these questions before, I appreciate your patients and expertise. I was born with only half a brain, unfortunately it was not the technical side.
Lon Jett
"A computer once beat me at chess, but it was no match for me at kick boxing." (Emo Philips)
Comments
Start with the flowchart
The multisite flowchart isn't complete, but should be a good starting point.
If you want one database with separate domains, see Domain Access.
subdomains
Hello Boris, I finally deciced on 3 drupal installs; one on the main domain for the photo gallery, one for each sub-domain. Each has their own data base. My problem now is getting stuck trying to configure each site. When something doesn't work like it should I am spending hours trying to figure out how to fix it and sometimes causing something else to fall apart.
I have spent the past 4 hours trying to figure out why the images module won't recognize the default image path and changed the settings on the fckeditor so it doesn't show when I try to edit content. I keep going around in circles.
Lon Jett
"A computer once beat me at chess, but it was no match for me at kick boxing." (Emo Philips)
Lon Jett
"A computer once beat me at chess, but it was no match for me at kick boxing." (Emo Philips)
Maybe it's too late, but I
Maybe it's too late, but I would still suggest multisite if there is much shared information between the websites since it'll save lots of time on management and maintenance. I used to build a bunch of websites using Domain Access modules and I don't think it's hard to setup. The only tricky thing I encountered may be the table prefix settings.
Cheers,
Steve
A Drupal Developer
Domain Access Feedback
TechSteve
Have you used both Multisite and Domain Access? I still am not sure that I understan the difference beetween the two and why I would select one over the other. I have the multisite module installed for a project that I have started and I hope I didn't select the wrong approach. Any insight would be greatly appreciated.
Thanks Steve
Use Domain Access if you
Use Domain Access if you would like to easily share content and/or users amongst sites and all sites will be using the same modules and configurations. Use Drupal's standard multisite if sharing content and/or users amongst sites is not important or you want each site to use varying modules and configurations.
The Boise Drupal Guy!
I don't think we could say a
I don't think we could say a solution is wrong or not. For a particular niche, some solutions may be better and some might not be the best to approach the goals. My system requires one corporate website and over 20 affiliated websites, they share the same users and have quite similar designs; each of the websites has both generic content (shared cross all websites) and specific content (only for one website). For my case, there is quite a lot information need to be shared, so I chose 'Domain access' module and related modules, such as Domain blocks, Domain alias, Domain sessions, ...
A Drupal Developer