On 25/03/13 22:57, Yogesh Saini wrote:
I beleive you should use domain module to achive it. Ànother option is that u can use default multisite setup of drupal which contain different database for each its domain but in this case u can't share contents to its sub domains. So, I beleive u should go for domain module itself.
I have been thinking domain too, because superficially it provides the common membership and overall appearance.
However, when I created /About at example.com and /About at raiders.example.com I discovered I had two About menu items.
In the case where there are colliding menu items, I want the more specific one chosen, not all that the viewer is permitted to see.
Multisite might work with some hacking... Obviously I have to do something about the user table, and maybe shared content.
On Mar 25, 2013 7:53 PM, "John Summerfield" <summer@js.id.au mailto:summer@js.id.au> wrote:
I am trying to create a website for a club, we'll call it's domain example.com <http://example.com> example.com <http://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 <http://friends.example.com>, raiders.example.com <http://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 <http://example.com>. For example, example.com/About <http://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 <http://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 <http://raiders.example.com/About> but not the one at example.com <http://example.com> or friends.example.com <http://friends.example.com>. What happens is that a user registered for both example.com <http://example.com> and raiders.example.com <http://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/ ]