Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By sunshinelock on
I just installed Drupal 6.6 and read the documentation to get oriented to the software.
This is my scenario:
I run several sites right now: (this is just for visualization)
example1.com
example2.com
example3.com
All are different sites, different content. I maintain example1.com and example2.com and have somebody that updates their own content on example3.com, but I don't allow them to change their template (currently running on Typo3 but trying to migrate to Drupal).
I just registered 2 more domains, example4.com and example5.com.
I want to offer other people a free website where they can choose to use either example4.com/customer1 or example5.com/customer1, or they can use both web addresses if they like, yet point to the same information. Customer 2 will have a site such as example4.com/customer2. Each site will not link to the main page of example4.com or example5.com. Pages will be served such as example4.com/customer2/page1 or example4.com/customer2/page2.
I also want them to be able to upgrade their site for a fee (I guess I need some sort of subscriptioning module if one is made) that removes the ads on their pages for the paid length (a year or month or whatever).
I have a test page up on example4.com and managed to get a secondary menu going that I probably can figure how to display each menu for each customer site, but I'm having difficulty in figuring my next step at getting multiple sites such as described above deployed.
Do I need modules to handle this, or what? Or is this handled by the multi-site setup under sites/default etc? http://drupal.org/getting-started/6/install/multi-site
Can I get a few links to known Drupal installations that do as I requested?
Comments
Additional
Additional clarification:
The potential "customer" of customer1 will surf directly to the site by typing example4.com/customer1. They will not be seen any login screen. They should just get a seamless impression about customer1's site. Customer1 however can log in by going to example4.com/admin or whatever he needs to to get to his content management menu, which will never be seen by other casual surfers.
I downloaded "Domain Access"
I downloaded "Domain Access" and the description sounds like it's a good start. 1) Is this really what I need?
2) What is an "Organic Group"? What do the modules for that do?
3) Is there a good subscription module to turn ads off for a paid amount of time?
I'm not sure I fully
I'm not sure I fully understand the nuances of your use case, but I do have a couple of comments:
1) if you need to share content then you probably want the domain module rather than multisite (which was designed to run separate sites from a single codebase).
2) I'm not sure about the ad part, but drupal has basically 2 ecommerce modules that can handle subscriptions: ubercart and ecommerce. Also, for a less full featured solution, it seems the lm_paypal module is coming back to life.
3) One thought about the ads part-- If you place your ads with blocks, and give paid users a different role then authenticated users (ie "paid'), then you could probably use block visibility code to show ads only when the 'owning' user does not have the 'paid' role associated with their username. This could get very complex though.
4) if you don't want users to see the login block, simply turn off the block at admin/build/block. The ability to login will still be available at example.com/user.
5) organic groups does exactly what it's project page says it does: enable users/admin to create groups of users. To see one implementation just take a look at http://groups.drupal.org.
hope that helps some...
===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz