Theme support

The approach is right. The trick will be making different theme configurations possible.

For example:

- Site A uses Garland with the default color scheme.
- Site B uses Garland with with 'Belgian Chocolate'.
- Site C uses Bluemarine.

This will be slightly more complex, and those settings should probably go into a {domain_theme} table. The settings would be loaded during hook_init().

After I get the core module in place, I'll devote some time to a domain_theme.module. But feel free to keep working in this direction.

The MySite module (which I also maintain) has some theme-switching features for users. You might take a look at how that is implemented.

The trick will be allowing user themes to override domain themes. Load order could be a factor here.

Note that I committed to HEAD the start of some internal APIs.

The only one of note right now is hook_domanlinks(), which is simply used to present links on the admin screen.

Since some development is ongoing, you should patch / code against HEAD.

Right. If you need other hooks, post them here.

One note: you can't fire module hooks during hook_init().

One second thought, post hook requests in this new issue.

FYI:

I'm actively developing the following:

- Domain Navigation == adds navigation block and menu options.
- Domain Content == allows affliate editors to perform batch editing processes.

As a result, I'm finding lots of places to reduce code overhead by creating simple functions. For example:

/**
 * Assigns the default settings to domain 0, the root domain.
 *
 * This value is used throughout the modules, so needed abstraction.
 */
function domain_default() {
  $default['domain_id'] = 0;
  $default['sitename'] = variable_get('domain_sitename', variable_get('sitename', 'Drupal'));
  $default['subdomain'] = variable_get('domain_root', '');
  $default['path'] = domain_get_path($domain);
  return $default;
}   

So the HEAD branch is definitely not stable. Expect major commits this week.

If you have other 'helper functions' that you need, post away.

And if you have some code for Domain Theme, I'd love to see it.

I've just installed Domain Access and it's a fantastic solution to what I am sure is a common problem. One request and an offer:

As you're developing the multi-theming function, one thought would be to work with the Taxonomy Theme developers to include HTTP_HOST into their list of things that gets evaluated when it decides to load up a theme. I find that I use Taxonomy Theme all the time, and would use it in addition to any theme switching function that you guys would work up.

Just a thought: it might make it easier for you to do this than to build your own solution.

I'm willing to help out as much as I can on this (testing, reporting, coding--my skills are limited).

That's a good head's up. I think we need to be sure that it works with Taxonomy Theme, but I prefer not to introduce an external dependency.

For now, I have committed a stripped down version of canen's code.

The current Domain Theme module only lets you select a default theme for each domain. Other settings must be entered through the normal theme administration screen.

Advanced theme settings functions may not need to be developed.

I'm going to mark this 'by design' to indicate that the issue is still active, but a decision has been made. That decision may be revisited if people contribute more code.

@canen -- I loved your first pass at the module, but it may have been too complex for most users.