Hello,

I am trying to eliminate 8 seperate CMS installs that can't handle a multi multi domain setup, get one centralized database and administration panel, and run each of these sites as if they were seperate.

Each of the sites are simple 5-10 page sites with the same template (Different Banners), and 1-2 people that edit each site independently. (So 8-16 people that deal with 1 of the 8 sites).

The 48 address nightmare that killed the administration on the other CMSs...

The main site has 3 domain names. I run the site so I just used html and php instead of messing with CMS.

domain.org
domain1.org
domain1.com

The 8 websites have their own virtual hosts which are more or less sub domains, but the www. version isn't automatic and must be created as another virtual host or the www. dosn't work.

So site 1 could be accessed from any of theses addresses:

site1.domain.org
site1.domain1.org
site1.domain1.com
www.site1.domain.org
www.site1.domain1.org
www.site1.domain1.com

Yes, thats 6 virtual hosts per site or 48 virtual hosts for all 8 sites. It might be confusing, but it works I just need a CMS that can handle it...

------

The user/editor aspect....

Each site is for a sub group.... In the past they all used freeweb and other solutions like that to build their sites. Then they chose to run everything from their existing web host and ban the use of external hosting stuff.

Most of the problem was I didn't have time to find a proper solution so I had to jerry rig something to work for the short term till I could find something better...

The problem with most of the other CMS systems out there is they are too complex for the users to run and/or the documentations was a nightmare as there wasen't a dummies guide to building their sites.

So the last question I have is on the user administration site.

Is this a simple solution for the end user to build the pages and run the site? And is there a WYSIWYG editing function or can one be easily added as these people don't understand ANY HTML. They understand using MS Word...

Thanks
AMDbuilder

Comments

luno’s picture

It's no more confusing than most other virtual hosting installations.

Start with one domain, "example.com". Assume you have several "secondary" vhosts, like "www.example.com", "foo.example.com" and "bar.example.com", and the primary vhost is "example.com". Each secondary vhost needs an index.php to redirect to the primary site. It's a one liner, as follows:

<?php header('Location: http://example.com'); ?>

At the primary site, you just need a Drupal installation. While there's no MS-Word plugin (yet ;) for Drupal, there are a number of WYSIWYG editor modules, you can take your pick.

For user-owned sites, It's easy to add roles to a Drupal installation - in your case, you'd probably want an "admin" role for the site users that didn't grant full administrative access, but still had permissions to create and modify content.

If the sites have separate content, the easiest way to administrate them is with separate databases. As you learn more about Drupal, you'll discover that there are tricks (and modules) to allowing unique content for different virtuals that point to the same database, but it's not the easy way to do it.

AMDbuilder’s picture

Hello,

It sounds like your recommendation is just 1 install with it's own database for each site, and then create a redirect folder to send everyone to the main address.

The one thing I was hoping to accomplish with all this is to get more time away from this client's stuff.. As is even simple things are confusing me now... (I need vacation..)... Anyways within reason can I reduce things down to 1 administration panel or would I be better off just sticking with 1 per site?

Thanks
AMDbuilder