Domain Access & i18n language specific counts

1. Changes in term_node_count.install

Schema
a. The schema no includes columns for "gid" (domain_id) and "language" (node language via locale module)
b. The primary key now contains 3 items: 'primary key' => array('tid', 'gid', 'language')

First install: pre-filling the count table
a. adapted the query to cycle through domains & integrate with language

	// first we'll count all the number of published, current revisions for each term that has at least one
	$sql = 'SELECT domain_id FROM {domain}';
	$result = db_query($sql);
	while ($row = db_fetch_object($result)) {
	  $sql = 'INSERT INTO {mt_node_count} (tid, gid, language, node_count) (SELECT tn.tid, da.gid, n.language, COUNT(tn.tid) FROM {term_node} tn LEFT JOIN {node} n ON tn.nid=n.nid LEFT JOIN {domain_access} da ON n.nid=da.nid WHERE n.status=1 AND da.realm="domain_id" AND da.gid=%d GROUP BY tn.tid)';
    db_query($sql, $row->domain_id);  
	}

This code correctly filles the table with counts per domain/language combination, e.g. 0-en, 0-fr, 2-en, 2-de etc., for each term tid.

2. Changes in term_node_count.module

a. The function term_node_count_update needs two extra arguments, $node->language and $node->domains, which are already available in _nodeapi hook.
So change to all function calls to term_node_count_update($tids_to_update, $node->language, $node->domains);

b. That function then cycles through each given $node->domains as $gid (domain_id) and $node->language.

We use a query of the type INSERT INTO ... ON DUPLICATE KEY UPDATE .... Thanks to the primary key triplet (gid, language, tid), we can safely update the counts correctly. Using only 1 query.

/**
 * Updates terms in mt_node_count given an array of tids.
 */
function mt_node_count_update($tids_to_update, $language, $domains) {
	// go through each tid provided, count the number of nodes attached
	// to it and update the mt_node_count table
	if (!empty($tids_to_update)) {
		$sql = 'INSERT INTO mt_node_count (tid, language, gid, node_count) VALUES (%d, "%s", %d, %d) ON DUPLICATE KEY UPDATE node_count=%d';
		foreach ($domains as $gid => $domain) {
      $counts = mt_node_count_count_nodes($tids_to_update, $language, $gid);
		  foreach ($counts as $tid => $count) {
        db_query($sql, $tid, $language, $gid, $count, $count);
      }		  
		}
	}
}

c. The function mt_node_count_count_nodes also needs two extra arguments, the only change we make is the query.The new query counts by language & given domain.

		$sql = "SELECT tn.tid AS tid, COUNT(tn.tid) AS count FROM {term_node} tn LEFT JOIN {node} n ON tn.nid=n.nid LEFT JOIN {domain_access} da ON n.nid=da.nid WHERE n.status=1 AND tn.tid IN (%s) AND da.realm='domain_id' AND n.language = '%s' AND da.gid = %d GROUP BY tn.tid";
		$result = db_query($sql, $tids_list, $language, $gid);

What is powerful about above changes, it works from any source domain, and any source language: the counts are always updated correctly.

3. Changes in term_node_count.views.inc

a. We want to filter our views by domain counts, so we simply add this (depends on domain.module):

  $data['mt_node_count']['gid'] = array(
    'title' => t('Term Node Count Domain ID'),
    'help' => t('The unique id key for the active domain.'),
    'field' => array(
      'click sortable' => TRUE,
      'handler' => 'domain_views_handler_field_domain_id',
    ),
    // Information for accepting a domain_id as a filter
    'filter' => array(
      'handler' => 'domain_views_handler_filter_domain_domain_id',
    ),
    // Information for sorting on a domain_id.
    'sort' => array(
      'handler' => 'views_handler_sort',
    ),
  );

-------------

Felt like writing up my changes, for others to learn from, and perhaps all of this can be an optional admin.setting for the term_node_count module.