[support] Domain Access

[Christopher M. Jones]

+1 For the problem of other modules not playing nicely with DA. My own 
example: twitter, when it posts the url of new content, does not seem to 
respect the originating domain of the post. Instead all links in the 
tweet point to the primary domain. Which is a problem if the post is not 
published there.

-Generally- though, I find these problems are surmountable. And they are 
not problems with DA but with other modules not following best 
practices. Unfortunately, it's impossible to see ahead to anticipate 
these problems for spec'ing. So definitely pad your estimate.

Also, I recently was disappointed that I couldn't use my hot new varnish 
/ pressflow deployment with DA. DA is not compatible with aggressive or 
external caching, as noted on the performance page.




On 10/07/2010 05:44 PM, Pablo L. de Miranda wrote:
> Hi Don,
> I have been working with Domain Access a year now. For your needs it
> will work very well, the primary problem is that another modules are
> not build with multiples domain in mind. One example is the contact
> module, you will have a unique contact shared in all your site, I`m
> modifing the contact core module to support Domain Access, but it
> wasn't approved yet as a new project.
> The module is very easy to use, no hard-code configurations are
> necessary, all the job are point a new domain to your drupal
> instalation and configure the Domain Access to receive the request
> coming for this domain and the magic happens. .
>
> Att,
>
> Pablo Lacerda de Miranda
> Software Engineerer
> Ci&T - Campinas
> pablolmiranda at gmail.com
> +55 11 8701-1086