In this article we discovered that one of these Domainers is, according to the journalist, the Keyser Söze of the parked domains, called Yun Ye. Porter's most recent posts
Keeping the name of its owner, Pat Francis, since 1976, and going returning a creation or so before that in very identical type as. which Antique Wine is known for
So, a disconnection occurs in the novel between the creative male mind and the reproductive female body, as Victor perceives the relationship as fatal. More
Perfect Module for filltering content and users by domain
it's perfect solution to make multisite using one system i recommend this module every thing is easy and well documented also there is a video from a confrunce it's very good , you will find it in the module page download it .
one notes for new people DON'T enable Domain Strict because its force users to be assigned to a domain and the anonymous not assigned to any domain so the anonymous will not be able to see the content that assigned to a domain just use it if you need such a thing .
This module saved my life
...Well, working hours of it, anyway.
My organization has a public site and an employee intranet, and domain access is excellent for maintaining these two sites simultaneously and sharing some (but not all) content between them. It has a very complete set of features for managing content, paths, menus, themes, and so forth. The user interface is also straightforward, and the documentation is unusually thorough.
If you have a small number of related sites, especially sites that need shared user profiles or content, do not fall into the trap I did and spend weeks mucking about with multisite configurations. Use this module instead.
Does what it says it does, with a couple caveats
First off, I'd like to compliment the developers here for being so focused and responsive during the creation of this module. I think this is probably the best documented Drupal module I've used, and it does what it says it does: allows you to use a single code-base across multiple domains and sub-domains, plus, easily create critical exceptions.
The way it does this is a little tricky, and my main useability compliant is that it really wants you to make system-wide changes in the primary domain, but doesn't force you there. Consequently, in the heat of the moment, its pretty easy to make changes you think are system wide, that aren't, and conversely, make configuration changes you think are subdomain specific, with interesting results.
Once you get the hang of it, it works very very well. Except for one upgrade early in the dev cycle, the module upgrades have been exceptional for how well they don't "break" things.
For certain kinds of projects, this module is/will be critical for implementing a straightforward, well-managed configuration and administration process. This should be incredibly useful for any medium-sized enterprise, with well defined departments, or any kind of organization who has tight- to moderately-tight relationships with affiliates. It probably won't work for organization with loose affiliates.
I haven't used it with Organic Groups, and suspect that might be an interesting can of worms, but for what I've been using it for, it's an excellent module. And when I've had problems, it has been easy to find the explanation and fixes in the documentation, (which, in my humble opinion, should be the gold-standard for Drupal module documentation).
Domain Access can revolutionize affiliations
Addendum since initial review: I have completed a simple example website using the Domain Access module. So far I installed the module, the helper modules I needed, figured out how to implement wildcard DNS so the subdomains are automatically added to the site, and installed the Shared Sign-On module. Next I will demonstrate how to use Organic Groups and Domain Access together. I mean to create a screencast in the near future as well and will update this review when that is complete.
I've been testing Domain Access with multiple domains, both second-level domains (e.g., example.com, examples.org) and subdomains (e.g., sub1.example.com and affiliate.example.com). I haven't found a client that is in need of affiliate web sites, but I have a few in mind that have wanted affiliate driven sites attached to there main website in the past. So, I'm hopeful to give a real world example in the future.
The main example given by the developers is www.skirt.com. If you visit that site you can see Domain Access in action with the choose another skirt drop-down menu.
Essentially the "Domain Access project is a group of lightweight modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database."
The module is both easy and difficult to install and use, and depends on your needs how many of the helper modules you'll need, and what your level of DNS and sever experience you have. I already operate a dedicated server and understand dns pretty well. Conceptually I think it will be difficult for newbies, but the installation is fairly simple for seasoned developers. The Documentation is first-class and maintainer agentrickard is on top of the modules needs and tickets.
Using Organic Groups and Domain Access does work together but I found the need to follow this issue to make it work well: Anonymous user permissions when integrating with OG.
I've found most helper modules that are included to be essential, such as Domain Configuration, Domain Content, Domain Navigation, Domain Prefix, Domain Theme, Domain Views. I especially like the fact that Domain Prefix provides "enabling select database table prefixing for use with subdomains." So for instance each subdomain can have their own logs (watchdog). The user interface isn't too shabby either.
I'll post something more here once I either have a client with this need, or set up an example website.
Scott Blackburn | Web Developer
Droplits: Sustainable & Systemic Web Solutions
If you are looking for help with Drupal modules and themes, and any Drupal website development contact me at http://droplits.org/contact