[support] Domain Access alternatives..

Wipe_Out wipe_out at users.sourceforge.net
Tue Oct 2 14:04:33 UTC 2012


Hi,

I have a single web application that we have built on Drupal that makes
extensive use of the content_access module for managing access to the
various bits of information stored on the site for different roles and
individual users.. The company has two "identities" that have different
branding and currently run two sites..

The objective is to have a single "site" for both domains.. On a simple
site the Domain Access module is perfect for this but its design and the
design of Drupal's node access system means it doesn't play well with
content_access.. So I am looking for an alternative setup..

So far I have found ThemeKey that looks like it will switch the theme
nicely for the domain being accessed..

Things I am having a hard time working out..

1) For each "domain" I need a different "home" page.. Any suggestions how
to have <front> show a different page depending on the domain?

2) The meta tags need to be different depending on the domain being
accessed..

3) Separate "contact us" form for each domain..

I have just started looking at the "context" module and the
"context_condition_theme" module but these don't seem to be solving the
problems for me.. I was going to use context to manage block placement for
each "site" but it doesn't seem like its able to do this for this type of
arrangement where more than one theme is being used.. The core blocks
module for all its short comings seems to be able to do this more easily..

My other alternative would be to keep the separate site for "marketing" and
somehow redirect the login block (or just create a login link) that
redirects into the primary site and then just tweak the branding to make
the user feel comfortable even though slogans, meta tags, titles and urls
won't be right for that "domain"..

Thanks..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20121002/87e726ec/attachment.html 


More information about the support mailing list