Posted by noahlively on November 30, 2010 at 11:58pm
5 followers
Jump to:
Issue Summary
I have been looking through the modules and the issue queue for something that provides a "current domain" context through ctools. I have not found anything yet.
Before I begin writing a context plugin, is there a compelling reason why one shouldn't be created?
Thanks,
Noah Lively
Comments
#1
No reason at all other than time. It should be a patch against this module, though, which is split off from the main module for faster development.
Unless Domain Ctools actually has what you need, which I doubt.
Current domain is a global value that most things are sensitive too, so I don't quite now what you would gain with a Ctools context. There is also a context module plugin. http://drupal.org/project/domaincontext
#2
Panels selection rules was the application I wa thinking of.
#3
I don't think I have messed with that. Take a look at what Domain CTools provides, and patch against HEAD as needed.
#4
I needed the same, however if you have the Token module installed, which most do, you can use the Token context and make the identifier "Domain" and the Keyword "domain" and magically the domain variables appear.
I used the %domain:domain-subdomain-raw to get the sub-domain name
#5
I suspect that is the proper solution, yes?
#6
I think it would be neater to have a proper context plugin for this.
My use-case is that I use the panels cache, with context-based granularity, with the same panel on different domains. Inside the pane are views that are domain-sensitive, so when the panel caches on one domain, it caches then spits out the wrong view content on the other domain...
Tokens are a bit of a hack...
#7
Those are two different issues, really.
Patches welcome.
#8
Bumping