- 🇺🇸United States bluegeek9
Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade → .
I have a live site at www.example.com and a development instance at devel.example.com, a direct copy on the same server running under that subdomain.
I need to use a subdomain to create a wholesale site that will use the same content and products, hence the Domain Access module.
So the final setup should be:
- www.example.com
- wholesale.example.com
But first it needs to be configured on the development instance so I can actually test things and reconfigure and develop to ensure things stay working, then make it easy to export via Features. So:
- devel.example.com
- wholesale.devel.example.com
It seems Domain Alias's would be the answer, somehow. But I'm not certain how to set them up for this use case. The README is helpful, but doesn't specifically address it. And I'm confused about what NOT REDIRECTING an alias actually does.
Should my main domains, even on development be example.com and wholesale.example.com, and then those are aliased? But if they are aliased with devel.example.com and wholesale.devel.example.com respectively, wouldn't people just get redirected to the live site?
I have looked at http://drupal.org/node/766970, but am still confused. How does that actually help?
Any insight would be greatly appreciated.
Thanks!
Closed: outdated
3.8
- Domain Alias
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal 7 in End of Life and no longer supported. We encourage you to upgrade to a supported version of Drupal. For more information, see https://www.drupal.org/upgrade → .