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?
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. On Mar 25, 2013 7:53 PM, "John Summerfield" summer@js.id.au wrote:
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/ ]
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/ ]
On Mon, Apr 1, 2013 at 11:21 PM, John Summerfield summer@js.id.au wrote:
Multisite might work with some hacking... Obviously I have to do something about the user table, and maybe shared content.
Look at the examples given in settings.php. You can state common user table and even change the authentication method.
-- Earnie -- https://sites.google.com/site/earnieboyd
On 02/04/13 19:56, Earnie Boyd wrote:
On Mon, Apr 1, 2013 at 11:21 PM, John Summerfield summer@js.id.au wrote:
Multisite might work with some hacking... Obviously I have to do something about the user table, and maybe shared content.
Look at the examples given in settings.php. You can state common user table and even change the authentication method.
-- Earnie -- https://sites.google.com/site/earnieboyd
My phrasing was bad. I've seen examples sharing users and also taxonomy. I presume roles & permissions are equally shareable.
I'm contemplating adding two fields to node, to reflect publishing domain and whether it should appear on other sites. By changing node, I will get all content types.
With a common user base, I don't see a need to for all the access controls added by the domain project. The specific content available will be determined by the domain name, viewers at Raiders will see Raiders content, at Friends only Friends.
Organic groups module will do what you want.
Pia
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/ ]
Hello John, there is a wealth of information on drupal.org, as well as quite a few references to external sites. Eljay
On Tue, Mar 26, 2013 at 2:38 PM, John Summerfield summer@js.id.au wrote:
On 26/03/13 00:21, Pia Oliver wrote:
Organic groups module will do what you want.
Pia
Thanks Pia, I will give it ago. Is there anything I should read, or videos I should watch?
-- John
-- [ Drupal support list | http://lists.drupal.org/ ]
Hi Guys,
There are some good videos here: http://modulesunraveled.com/organic-groups . Helped me out a lot in the past when I first started working with this module.
-T
________________________________ From: L.J.Bos eljay09@gmail.com To: support@drupal.org Sent: Tuesday, March 26, 2013 10:09 AM Subject: Re: [support] Domains, subdomains on D7
Hello John, there is a wealth of information on drupal.org, as well as quite a few references to external sites. Eljay
On Tue, Mar 26, 2013 at 2:38 PM, John Summerfield summer@js.id.au wrote:
On 26/03/13 00:21, Pia Oliver wrote:
Organic groups module will do what you want.
Pia
Thanks Pia, I will give it ago. Is there anything I should read, or videos I should watch?
-- John
-- [ Drupal support list | http://lists.drupal.org/ ]
On 27/03/2013 12:23 AM, Tim Linteau wrote:
There are some good videos here: http://modulesunraveled.com/organic-groups . Helped me out a lot in the past when I first started working with this module.
Thanks Tim.
I like personal recommendations over stuff I find by myself - it guarantees someone other than the author thinks they're good.
I've looked at the first one, I will view them more closely when my new test site's installed.
Hi All,
I'm using pdf_reader module google viewer to read pdf file. http://dev.cphpost.dk/sites/default/files/public/pdf/1609_CPHPost_3_web.pdf How can I change the page title and add site favicon ? and remove "sites/default/files/public/" from url ?
Thanks in advance!
Best, Li Xiuqing
On Tue, Apr 2, 2013 at 4:44 AM, Li li_xiuqing@hotmail.com wrote:
Hi All,
I'm using pdf_reader module google viewer to read pdf file. http://dev.cphpost.dk/sites/default/files/public/pdf/1609_CPHPost_3_web.pdf How can I change the page title and add site favicon ?
Just put your favicon.ico file in the DocumentRoot.
and remove "sites/default/files/public/" from url ?
There are several ways. What do you want it to do instead?
-- Earnie -- https://sites.google.com/site/earnieboyd
I just added favicon.ico to the site root and clean the cache. It's still not showing. any suggestion with changing page title text "1609_CPHPost_3_web.pdf " to something else?
http://dev.cphpost.dk/sites/default/files/public/pdf/1609_CPHPost_3_web.pdf
and remove "sites/default/files/public/" from url ?
There are several ways. What do you want it to do instead? The easiest way, which can work both for private file and public file.
Thanks Li
On 02-04-2013 13:52, Earnie Boyd wrote:
On Tue, Apr 2, 2013 at 4:44 AM, Li li_xiuqing@hotmail.com wrote:
Hi All,
I'm using pdf_reader module google viewer to read pdf file. http://dev.cphpost.dk/sites/default/files/public/pdf/1609_CPHPost_3_web.pdf How can I change the page title and add site favicon ?
Just put your favicon.ico file in the DocumentRoot.
and remove "sites/default/files/public/" from url ?
There are several ways. What do you want it to do instead?
-- Earnie -- https://sites.google.com/site/earnieboyd
I am far from an expert but took Emma Jane Hogbin's course, and for one project we used that. You could check her out http://drupal.org/user/1773 there is also good stuff here http://drupal.org/project/og?utm_source=Design+to+Theme&utm_campaign=292565b478-configdrupal_4&utm_medium=email
Pia
On 26/03/13 00:21, Pia Oliver wrote:
Organic groups module will do what you want.
Pia
Thanks Pia, I will give it ago. Is there anything I should read, or videos I should watch?
-- John
-- [ Drupal support list | http://lists.drupal.org/ ]
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/ ]
-
Earnie Boyd -
John Summerfield -
L.J.Bos -
Li -
Pia Oliver -
Tim Linteau -
Yogesh Saini