Closed (works as designed)
Project:
Context Domain
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Apr 2011 at 14:37 UTC
Updated:
30 Oct 2013 at 22:55 UTC
Doesn't PURL already do this?
Comments
Comment #1
patcon commentedSo far as I know, PURL+Spaces works for when you have the (sub)domain depend on the og/user/term/etc. But if, say, you just have the subdomain vary but the base install and DB stay the same, then I don't believe PURL helps. Maybe I'm wrong.
I'm considering how I could add some DNS A records for the domains we want to support -- say sub1.example.com, sub2.example.com and sub3.example.com -- but have only one drupal install in sites/all. (Might need to add symlinks from sites/sub2.example.com to sites/all dirs and settings.php).
The idea is that we could use Context Domain to grab the subdomain as a reaction, and then have the subdomains use different themes or display different block, or whatever.
Haven't tried it yet, but I've hot high hopes for this module helping provide an alternative to Domain Access (which strikes me as messy).
Comment #2
mdroste commentedThis is a great Module for different contexts on different Domains/Subdomain. I tried PURL+Spaces before, but can't get it to work like Content Domain. It's an ideal solution for Multisites with one DB.
Comment #3
colanPURL is for maintaining state between page loads while this module aims to provide a condition for the Context module that depends on the domain for a single page load.