Not really a support question but I was just wondering how does this differ from the multidomain module?

Thanks.

Comments

agentrickard’s picture

Off the top off my head:

- Domain manager does not require other modules. (multidomain requires single sign on).
- Domain manager does not require patching core.
- Multidomain supports HTTPS (and that was the primary driver behind its release).

Looking at the multidomain code:

- Multidomain uses vocabularies to assign content. (I don't like this approach.)
- Multidomain (like OG multisite) uses db_rewrite_sql instead of node_access for partitioning content.
- Multidomain (I think) supports different root domains (example.com and example2.com), whereas Domain manager only supports a single root (example.com and one.example.com).

There are some underlying similarities, but the code approach and assumptions are different.

canen’s picture

Thanks for the quick response.

I've been looking at the code and noticed the sub-domain thing. This may be easily solved by some Apache rewrites I think.

I'm working on a project that this module may prove useful for so thanks for the contribution. One more thing: Are there considerations for theme management or must all sites use the same theme?

agentrickard’s picture

Right, subdomains are handled by Apache. We use wildcard DNS, but virtual hosts work as well. (Some details will go in the README later this week.)

Theme management was not in scope for the original project, but could easily be handled by a sub-module, or rolled into the domain_conf module.

If you could whip up a quick domain_theme.module, that would be awesome. Just use hook_form_alter() and you should be in good shape.

canen’s picture

I created an issue for this.

agentrickard’s picture

Status: Active » Closed (fixed)

Awesome. Closing this one.