Hi Nick
What you want to do is quite achievable with Drupal. In fact, the
project I'm currently working on ivolves powering approx. 100 newspaper
sites from a single Drupal instance.
The solution involves setting up your Drupal instance with a combination
of Taxonomy plus the use of MySQL 5 views.
These 2 articles will explain the concept:
Managing multisite content from a single Drupal instance
(http://devbee.com/managing_multisite_content_from_)
Sharing Drupal tables between databases using MySQL5 Views
(http://devbee.com/node/4)
Restricting users can be achieved using the Taxonomy Access Control
module (http://drupal.org/project/taxonomy_access). As an example, I
don't want the editor of one newspaper to be able to CRUD content of
another paper. Therefore, a category called "Newspaper" is created and
newspaper staff are restricted to access based on that taxonomy term.
It actually took me a few days to research how to achieve this. However,
when I finally put it all together and built a proof-of-concept, it
worked like a charm.
Cheers,
Robert
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of 8bits Media
Sent: Friday, 7 March 2008 3:23 PM
To: [email protected]
Subject: [WSG CMS] Multisite CMSs
Hi there,
I was wondering if anyone new of a PHP or Ruby on Rails (preferably
open source) cms that has multi-site capabilities.
To clarify, what I am looking for is the ability for a user to manage
multiple sites, on multiple domains from within a single cms install.
Ideally, the cms would have the ability to restrict users so they could
only edit particular sites.
I've looked at a number of different systems (Radiant, Frog, Drupal,
Silverstripe, CMS Made Simple) but none of them really manage to pull
this off (yet). I've also had a look at Expression Engine, but although
this system has a module for this feature, EE isn't suited to the
applications I want to use it for.
At the moment, I'm looking at extending Radiant to have these features,
as it does already have a multi-site extension, but I would rather find
a system that had community support for this feature, as changing the
permissions structure within Radiant goes beyond just creating an
extension.
Thanks,
Nick.
**************************************************************
Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
**************************************************************
