The architectural challenge we face is wanting shared users, shared content and shared user generated content across multiple domains under Drupal 7. Each domain will have a significantly different theme. So far so good - all in domain access' sweet spot. The challenge is that we also want significant functional differences between the sites running on each domain - for example, some will be Facebook apps, others will be full sites.

Our initial thought was to use domain_prefix and split out the functional control tables but not only is this module not yet operational under D7, it feels like this architectural approach is going to open a truly scary Pandora's box of complexity and maintenance issues.

Any thoughts or recommendations on how best to achieve this?

Comments

nightlife2008’s picture

nightlife2008 commented

I'm currently also looking for how to share / separate activated modules.
I was also on the Domain prefix path, to prefix the system table but as you mention, it looks an unmaintainable solution which would otherwise be simple with separate sites/X.com/modules folders.

I hope someone figures this one out, or it gets bumped into Domain Access development!

/Kim

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

It's a nasty problem, and you are both right that Domain Prefix on the {system} table will lead to a nightmare, largely due to internal Drupal caching (such as the registry).

Really, Drupal core doesn't give us a good way to handle what you are after.

Potentially, you might be able to use the new Domain URL module to force canonical URLs for all content pages, but I think you're really hitting an architectural problem that core imposes. You might be better off using multisite (or separate sites with shared tables) and some form of Feeds / Migrate / Services to share content.

See http://drupal.org/sandbox/agentrickard/1080434 for the canonical URL option.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Closed (works as designed)