For those who attended the 'Affiliated Sites' presentation in Barcelona -- or who I told about the module otherwise. I have committed the initial code for the Domain Manager module. http://drupal.org/project/domain Documentation should be finished by end of week. In a nutshell, it uses registered third-level domains and node_access() to provide an affiliated content model. The site(s) share all tables, but content can be partitioned to all sites, one site, or a selection of sites. See the demo at http://www.skirt.com/map - Ken Rickard agentrickard
Ken Rickard wrote:
For those who attended the 'Affiliated Sites' presentation in Barcelona -- or who I told about the module otherwise.
Thanks for posting this to the list. I've been writing a nearly identical mosdule from what i can tell by your description. I'm going to check itr out and see if there is overlap i can drop/contribute, etc. Thanks again. -- Michael Favia michael@favias.org tel. 512.585.5650 http://michael.favias.org
On 10/2/07, Michael Favia <michael@favias.org> wrote:
Ken Rickard wrote:
For those who attended the 'Affiliated Sites' presentation in Barcelona -- or who I told about the module otherwise.
Thanks for posting this to the list. I've been writing a nearly identical mosdule from what i can tell by your description. I'm going to check itr out and see if there is overlap i can drop/contribute, etc. Thanks again.
What about http://drupal.org/project/multidomain and http://drupal.org/project/pressflow_multidomain and I think even one more that I can't find at the moment. Regards, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg
On 10/2/07, Greg Knaddison <greg@pingvox.com> wrote:
What about http://drupal.org/project/multidomain and http://drupal.org/project/pressflow_multidomain
and I think even one more that I can't find at the moment.
All slightly different. As is http://groups.drupal.org/hostmaster2 Domain Manager (a misnomer a bit, I think), is optimized for the whole subdomain / shared database....not actually managing domains. We'll likely have a couple of these, since the goals for sharing content / users / etc. are all slightly different, as is managing lots of separate DB run sites for hosting etc. -- Boris Mann Office 604-682-2889 Skype borismann http://www.bryght.com
Some comments based on all the above. There is a little domain management -- we use Widlcard DNS, so we actually manage the active subdomains with the module. I looked at the available options. There are several modules that are similar (OG multisite, and multidomain come to mind). None of the modules hit our use case. And pressflow_multidomain has no releases, so that's right out. See http://drupal.org/node/180225 for some other notes on multidomain. The five important differences for Domain Manager -- which I may rename Domain Access, since that's what it is -- are as follows: - It uses node_access() instead of db_rewrite_sql() for partitioning content. And the 'realms' that users belong to are based on the subdomain they are currently viewing, not on any form of group membership. - Content can be assigned to all domains, select domains, or just the parent site. (Which is the same as the other modules.) - If you don't have the 'set domain access' privilege, you are not even presented with a choice during node creation or node edit. In those cases, the node_access() rules are set based on configuration options and the currently active subdomain. The module is written this way so that editors can't screw up the system. In particular, I don't favor using vocabularies for partitioning content since the UI is prone to human error. - Optionally, you can also use the module to define editorial access to content, based on assigning editors to specific subdomains. - We separate editing privileges out into a hierarchical system. National editors can edit all nodes ('administer nodes'), where local editors can only edit nodes that belong to their domain ('edit domain nodes'). We also, btw, have a trick for selective table prefixing inside of settings.php which I'm working on a UI for. I'm not currently doing anything with menu entries, however, since the site we developed for used Flash navigation (so we used that mechanism instead of menu.module). The plan is to create a series of small modules that add functions. See http://drupal.org/node/180264 for example. All of this backstory will go into the module documentation -- and it was part of the Barcelona presentation. People I spoke with were anxious to test the module, so it's in cvs a little ahead of schedule. Hope to have a proper release by end of month. - Ken Rickard agentrickard On 10/2/07, Boris Mann <boris@bryght.com> wrote:
On 10/2/07, Greg Knaddison <greg@pingvox.com> wrote:
What about http://drupal.org/project/multidomain and http://drupal.org/project/pressflow_multidomain
and I think even one more that I can't find at the moment.
All slightly different. As is http://groups.drupal.org/hostmaster2
Domain Manager (a misnomer a bit, I think), is optimized for the whole subdomain / shared database....not actually managing domains.
We'll likely have a couple of these, since the goals for sharing content / users / etc. are all slightly different, as is managing lots of separate DB run sites for hosting etc.
-- Boris Mann Office 604-682-2889 Skype borismann http://www.bryght.com
Hi Ken I did a very similar module based on vocabularies but did not release it to the community yet. I also implemented the possibility to override variables and menu entries on a per-domain basis. Source is available here: hxxp://znerol.ch/files/sitevariants/ The site where the module is installed has some special content for different regions (just like yours) and some theme gimmicks (like the picture in the header). hxxp://bern.openwireless.ch/ hxxp://sg.openwireless.ch/ FYI: I plan to move away from that mechanism in favor of the standard way of sharing tables using sites/bla/settings.php and possibly using feeds and aggregators to link to shared content on a special subdomain for two reasons: * My users often where very confused about the fact that the changes they make to "their" content will be visible on other subdomains too. * I don't like the fact that the very same content is reachable using different URIs. * The goal of our site is to build a community platform and only separate the few things which actually are different amongst the local projects like some network-admin-stuff, locative information and some status and project information... If you find some interesting bits in the code feel free to just take it for your project. Lorenz On 02.10.2007, at 01:17, Ken Rickard wrote:
For those who attended the 'Affiliated Sites' presentation in Barcelona -- or who I told about the module otherwise.
I have committed the initial code for the Domain Manager module.
http://drupal.org/project/domain
Documentation should be finished by end of week.
In a nutshell, it uses registered third-level domains and node_access() to provide an affiliated content model. The site(s) share all tables, but content can be partitioned to all sites, one site, or a selection of sites.
See the demo at http://www.skirt.com/map
- Ken Rickard agentrickard
participants (5)
-
Boris Mann -
Greg Knaddison -
Ken Rickard -
lorenz schori -
Michael Favia