Some comments based on all the above.<br><br>There is a little domain management -- we use Widlcard DNS, so we actually manage the active subdomains with the module.<br><br>
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.
<br><br>See <a href="http://drupal.org/node/180225">http://drupal.org/node/180225</a> for some other notes on multidomain.<br><br>The five important differences for Domain Manager -- which I may rename Domain Access, since that's what it is -- are as follows:
<br><br>- 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.
<br><br>- Content can be assigned to all domains, select domains, or just the parent site. (Which is the same as the other modules.)<br><br>- 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. <br><br>- Optionally, you can also use the module to define editorial access to content, based on assigning editors to specific subdomains.<br><br>- 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').
<br><br>We also, btw, have a trick for selective table prefixing inside of settings.php which I'm working on a UI for.<br><br>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).<br><br>The plan is to create a series of small modules that add functions. See <a href="http://drupal.org/node/180264">http://drupal.org/node/180264</a> for example.<br><br>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.
<br><br>Hope to have a proper release by end of month.<br><br>- Ken Rickard<br>agentrickard<br><br><br><div><span class="gmail_quote">On 10/2/07, <b class="gmail_sendername">Boris Mann</b> <<a href="mailto:firstname.lastname@example.org">
email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 10/2/07, Greg Knaddison <<a href="mailto:firstname.lastname@example.org">
email@example.com</a>> wrote:<br><br>> What about<br>> <a href="http://drupal.org/project/multidomain">http://drupal.org/project/multidomain</a><br>> and<br>> <a href="http://drupal.org/project/pressflow_multidomain">
http://drupal.org/project/pressflow_multidomain</a><br>><br>> and I think even one more that I can't find at the moment.<br><br>All slightly different. As is <a href="http://groups.drupal.org/hostmaster2">http://groups.drupal.org/hostmaster2
</a><br><br>Domain Manager (a misnomer a bit, I think), is optimized for the whole<br>subdomain / shared database....not actually managing domains.<br><br>We'll likely have a couple of these, since the goals for sharing
<br>content / users / etc. are all slightly different, as is managing lots<br>of separate DB run sites for hosting etc.<br><br>--<br>Boris Mann<br>Office 604-682-2889<br>Skype borismann<br><a href="http://www.bryght.com">