Domain Access: Adding unique body tag id, for CSS Injector

Patches welcome.

New features go in 7.x.3.

In the interim, you can do this quite easily in template.php. Just read the global $_domain value or use domain_get_domain().

Let's add a token-based element to BODY that can be either an ID or a CLASS, as a setting.

Has this been implemented yet ? It's a great idea.

Let's add a token-based element to BODY that can be either an ID or a CLASS, as a setting.

Nope.

There are a few other cases where this is useful, especially if your domains share a common theme and you just want to change a background color.

Same use case here.

I use the same theme on a few domains, but have different content.

Would like to have a body class to make more subtle changes and not maintain a few themes.

Here's a use case:

We are using Domain Access to centralize administration for ad-campaign landing pages at "vanity" domains.

Landing pages must frequently have highly-customized presentation -- i.e., custom entries in the stylesheet that pertain only to that domain (e.g. http://ourproductistasty.com/). [can also use Code Per Node or something like that, but that can be a maintenance headache.] Typically (in the theme we use) this is done by prefixing style rules with body.[page-identifying class] -- e.g., body.partner-landing-page.

In some cases, we need to set one of these landing pages as the home page. In the example case, body.partner-landing-page would not be present when that page is rendered as the home page of http://ourproductistasty.com/. The simple workaround is to use body.front, which is available - but that would affect the home pages of all other landing page "vanity" domains (e.g., http://ourproductisSAVORY/).

That's just one use-case. But this is just generally the kind of thing you'd find people using all the time if they had it. As noted, we can add it in any one of several ways in our themes, but if it's just there by default, even better -- less migration work when updating/upgrading themes, fewer maintenance issues.

I did it at the theme layer in template.php (Drupal 6)...

function MYSITE_preprocess_page(&$vars, $hook) {
  if (module_exists('domain')) {
    global $_domain;
    $vars['body_classes_array'][] = "domain-". strtolower( str_replace(' ','-',check_plain($_domain['sitename'])) );
    $vars['body_classes'] = implode(' ', $vars['body_classes_array']);
  }
}

Here's a patch for 7.x.3. Needs a test.

The patch exposes the following settings form (see attached). These values are returned as CSS-safe class names.

And a patch with tests. Committed.

I don't know how portable this is back to d6, but if someone wants to try, I can commit it.