So here's the deal. This is a higher education project. Currently there are vhosts for each site built off the primary domain in addition to subdomains. We're trying to consolidate multiple sites into one and reduce the overhead of running multiple Drupal installs. While Domain Access handles the subdomain issues we're running into great, I haven't seen a way to use this module to control a branch off the primary domain. Here are some examples of what I'm talking about:

  • university.edu
  • college1.university.edu
  • college2.university.edu
  • college3.university.edu
  • college3.university.edu/department1
  • college3.university.edu/department2
  • college3.university.edu/researchgroup1
  • college3.university.edu/researchgroup2

So the issue comes into play at college3's subdomain. Specifically, the relative departments that are built off that primary, subdomain need to be treated as separate sites. Similar to how Domain Access treats subdomains.

Some people may think this is crazy but here's the logic set forth from the powers at be. And this may change, if it has to.

For branding purposes, the colleges are assigned subdomains. Then they can assign departments sites relative to the college association. For example, the College of Arts and Sciences would have something like cas.university.edu Then the departments under that college, say... Biology, Dance and Philosophy would need their own sites built relative to the college's subdomain, not the primary domain. Like this:

  • cas.university.edu/biology
  • cas.university.edu/dance
  • cas.university.edu/philosophy

Does anyone know if this is possible to control with the Domain Access module? The relative domains. If not that's fine. We'll have to talk with our branding team and let them know we're going to change our strategy and to go to biology.university.edu, dance.university.edu and philosophy.university.edu if we have to reduce our overhead.

I hope all that made sense.

Thanks for input everyone. This module is very awesome, I just want to make sure we're setting things up correctly and not expecting this module to do something it can't.

- Ryan

Comments

agentrickard’s picture

There is a test module, but it isn't ready for production. https://drupal.org/sandbox/agentrickard/1175752

Using subdomains is more reliable. I'm also not sure how to handle subdomain.example.com/foo. The current Domain Directory code assumes that *.example.com/foo is the 'foo' domain, which is not what you seem to be suggesting.

agentrickard’s picture

[Edit]

This comment was posted to the wrong issue.

agentrickard’s picture

Status: Active » Closed (works as designed)