Add support for assigning nodes to domains by taxonomy

Here's an updated patch. It's more or less working but needs refining. The update script takes care of creating a vocabulary and adding terms to it for each existing domain. Adding a node to a domain's category produces two effects:

* the node is only visible from that domain
* links to the node are to that domain.

Further thought is needed in the following areas:

1. Should this be optional or (as presently implemented) automatic on availablity of taxonomy module?

2. How should the primary domain work? Should it see all content, or only content assigned to its term? Or should this be configurable?

3. How should taxonomy interact with the two existing filter options (node type and path)? Which should take priority?

I'll continue testing and working on this. Comments and reviews meantime would be great.

Previous patch wrong, here's a better version.

Here's a patch with a number of bugfixes and improvements.

1. Improved install and update functions for initial creation and population of a dedicated vocabulary. Fixed an error in the module name of the vocabulary created.

2. Fixed a variable name error that prevented rewriting of nodes based on term.

3. hook_term_path() to link to the domains, which is presumably the expected behavior, rather than a taxonomy term.

4. hook_nodeapi() to remove domain term links from node view, since they aren't likely to be wanted.

5. Configuration option as to the desired bahaviour on the primary/master site, either (a) see all nodes or (b) see only nodes assigned to primary site's term.

Tested and this seems to be working well.

A summary of the result:

1. A taxonomy is automatically created for domains. Each domain has a term in the vocabulary. The term names and weights are updated when a change is made to the domain name or weight.

2. On the master domain config page, admins can decide whether . The node types assigned to the domains vocabulary are also editable here.

3. Users can assign content to a given domain through regular taxonomy selects.

4. When a node is assigned to a domain's term, two things happen:

a. links to that node point to the domain it's assigned to
b. that node is only visible on lists on that domain.

5. The other ways of assigning links to a domain - by path or by node type - still work. Taxonomy only affects nodes, and only nodes of node types assigned to the domains vocabulary. So, for example, it's still possible to have all 'page' nodes assigned to 'domain1'. To do so, leave 'page' out of the domains vocabulary, and claim all 'page' content on the 'domain1' configuration page.

Is there support for this direction? Any concerns? Any particular issues we should consider before applying this?

Note:

If you've installed my previous patch and then try this one, I'm not sure what the results will be. It would be best to first clean up the site by removing the previous data. First delete the domain vocabulary and all its terms. Then here's a suggested cleanup script to run (e.g., with devel module's PHP block, or in a page with the filter set to PHP):

// Delete the multidomain vocabulary variable.
variable_del('multidomain_vocabulary');
// Unset the registered tid variables.
$domains = variable_get('multidomain_sites', array());
foreach ($domains as $domain => $settings) {
  unset($domains[$domain]['tid']);
}
variable_set('multidomain_sites', $domains);

Thanks for trying the patch. Wading in and learning to apply patches is a great step to take.

Please note that the title is for the whole issue, not your followup.

There were changes made to the files since I posted the patch, here's a refreshed version, hope it works for you.

The closing PHP tag is optional and is left off by convention in Drupal.

It would be great if you could test and report back!

I'd like to apply this patch. I've been using it without issue on a site for some time now. Please post to this issue if you have any concerns before this is applied.

I'm attaching a patched version of the module for testing. I'm adding a .txt extension to the file so it will upload.

I've applied this to the DRUPAL-5 branch.