domain access

I pray this the right forum to post this inquiry...Hello, I am using Nodestream and domain access module. I have already created the sub-domains I needed. Now my question is how to 'push' (for lack of a better word) content to a particular sub-domain so it's (the article or advert is not visible to the other sub domains.)
The Domains created are as follows Nairobi, Nakuru and Test. Basically I want the articles meant for Nakuru to be either automatically routed using Taxonomy or manually using a sub-domain list/drop down.Need I say am a novice at this. Thank you

I'm thinking about technologies and options for a new multisite, edu multidomain project. Basic idea: people buy subscriptions to create custom domain sites.

Instead of pure sites for each domain, I'm thinking of using OG and some workflows for each domain. How capable is OG for custom full domain sites? Not just subdomains, 123.mysite.com but mysite123.com and mysite345.com all under the main code OG code base?

Hej,
Är det någon som har erfarenhet av följande:

Detta har hänt:
Det går inte att logga in på en av domänerna med IE
Provade bygga om behörigheterna
Efter det kommer gäster inte åt sidor som är skapade med views och panels där innehållet är satt att visa beroende på domän.

Någon som har varit med om detta tidigare?
Jag använder Drupal 6.20 och domain access

MVH Tomaz

OHO Interactive is developing a number of recorded Webinars discussing various topics randing from SEO to Mutli-site options to Themeing. Feel free to stop by a watch the webinars (free). Feel free to send along suggestions about what you'd like to see in the 'next' recorded webinar, etc.

www.oho.com/webinar

TL;DR:
Is there anyway to make Aegir and DA coexist happily?
After reading and meditating on it more I guess the big question is can Aegir provide an environment where different sites can share signon's and nodes?

Today at the pre-camp meetup we talked about keeping in touch regarding our current projects in our individual departments... so, for anyone interested, here's what I'm up to at the Department of Family Medicine:

Hello,
I am using domain access and domain theme to create subdomains and to theme them specifically.
Till I started working with Skinr/Fusion/Acquia Marina everything worked fine with setting theme configuration per theme.

Since Acquia Marina and Fusion is such a nice looking theme I decided to move to it, and setup the main domain.com to it, changing all I wanted.

Then I created another subtheme of Fusion (I copied Acquia Marina, and properly changed all of the names) and selected it for my subdomain.domain.com.

As a high school English teacher, I have set up several Drupal multisite installations over the last few years, and have been able to work through many of the usual issues, but I'm currently totally stumped by an issue: Everything works on my new site except the front page.

I just added a new site to my installation -- let's call it new.example.com. I went to new.example.com/install.php, and everything worked out fine. When I go to new.example.com/node, I get the front page. When I go to new.example.com/admin, I get admin. When I go to new.example.com/? I get the front page. Everything works fine whenever I supply any URL argument.

But when I type new.example.com, expecting the front page, it loads from the default multisite directory, not the new.example.com directory. The front page for my default site appears. When I tried removing settings.php in the default directory, new.example.com brings up the install script, as expected.

Nothing changes when I disable Clearn URLs. Any ideas? Thanks!

We are building a website with multiple sub-domains in Drupal. Each website should be treated separately with its own content. We want to share SOME content among sub-domains (not much), keeping in mind that SEO is of upmost importance. (no duplicate content among sub-domains). How would you approach this project? Would you use Domain Access or Subdomain module? or another module that I haven't heard about?

Hello,

I submitted a new module called domain_rules, which gives the strength of domain creation/deletion/etc. to the administrator using Rules.

I had to make it happen since existing modules such as domain_user didn't do exactly what I wanted. My goal was that when a certain user role create a certain content, I grab a CCK field out of it, create an alias to it, a new subdomain, set its theme (which, by design, shows the new created node as the front page), and set access to given users (in my case, anonymous).
When this node is being deleted, the domain is deleted with it...