[support] Domains, subdomains on D7

[John Summerfield]

On 26/03/13 00:21, Pia Oliver wrote:
> Organic groups module will do what you want.
>
> Pia

I have had a look at some videos, and I'm not sure it does what I want 
the way I want.

I want each club to have its own separate identity, but I suspect that 
if Pia were a member of Friends and Raiders, she'd see content from both 
all the time.

That isn't what I want.

My preference is for the clubs to be identified by domain name, and the 
domain module allows that.

I had a quick look at CiviCRM (however capitalised), and while overkill, 
it looks like it could fit right in, and it attends to many of the 
matters I would like, However, it requires MySQL, and I don't use MySQL.


The multisite feature allows me to share users without difficulty. drush 
doesn't really support it though. However, if I don't share much that 
might not matter.

Sharing designated content remains though.

I have an idea involving user code: basically tag content with "owning" 
domain and shareability info.

>
>
>> I am trying to create a website for a club, we'll call it's domain
>> example.com
>>
>> example.com should be the administration site, no club members per se,
>> although its registered users might be members of associated clubs, its
>> in order for that to be the case.
>>
>>
>> Associated clubs with have subordinate domains, so friends.example.com,
>> raiders.example.com and so on.
>>
>> It's also in order for people to be members of more than one club, and
>> they often are.
>>
>> Example.com will provide some general information that should be
>> accessed directly by all the subordinate clubs. On the other hand, each
>> club will provide information of its own, and that should be accessible
>> in a menu item, "club news."
>>
>>
>> Also, each club should be able to provide some specific information as
>> an alternative to that provided at example.com.
>>
>> For example, example.com/About would tell its visitors about the base
>> organisation. For example,
>> "We promote our sport....
>> "We have associated clubs here, there and everywhere."
>>
>> raiders.example.com/About would say that
>>
>> "We have these competitions....
>> "We have school programs at ....
>> "Our clubrooms are at 45 Raiders Way, Bordertown."
>>
>> and so on.
>>
>> What I want is for Raiders visitors see only raiders.example.com/About
>> but not the one at example.com or friends.example.com.
>>
>> What happens is that a user registered for both example.com and
>> raiders.example.com has, not one, but two /About links.
>>
>> An example of information that only Raiders can see is Raiders'
>> membership list. Our law requires that membership lists of all
>> incorporated bodies (in Australia that means Example Inc, Raiders Inc -
>> company names are generally titles Ltd or Pty Ltd) must be available to
>> members. For the present I don't propose to provide more than just the
>> names of members, but I do wish it to be available only to those
>> members, and not to General Public.
>>
>> Similarly, Club News would mean Raiders' news at Raiders, Friends' news
>> at Friends, but their news should be accessible through another menu choice.
>>
>> I have a working list of associated clubs, so switching between domains
>> is trivial. I an happy to have just one list of members, but they must
>> only see member's-only content from whichever site they are looking at
>> at the moment, and then only if they are members of that club.
>>
>> I have been trying to do this with the domains modules, but I am not
>> sure that the will let me do what I want without cutting code. I am
>> pretty feeble with PHP, but I might manage a small amount.
>>
>> Does anyone have any advice on how to achieve my ends? Is using the
>> domains modules my best choice, or should I look at something else?
>> --
>> [ Drupal support list | http://lists.drupal.org/ ]
>
>