Closed (fixed)
Project:
Open Atrium
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
12 May 2014 at 18:05 UTC
Updated:
29 Apr 2015 at 22:44 UTC
Jump to comment: Most recent
Comments
Comment #1
socialnicheguru commentedI found this issue: https://drupal.org/node/2042191
So is it only for subdomains
http://mysite.com/somegroup -> http://somegroup.mysite.com
I would like to make it
http://mysite.com/somegroup -> http://somegroup.com
will that later work?
Comment #2
jkingsnorth commentedDoes this issue help? #2291719: Separate domain names for different spaces
This really needs a documentation page creating - let me know if that issue helps and I'll change mpotter's comment into a docs page.
Comment #3
ericjan commentedMore documentation is very much appreciated! Which steps do I need to take to get this working?
In my case I would like to have my spaces available on a subdomain, so http://example.com/space1/subpace becomes http://space1.example.com/subspace
With all that is currently described in: https://www.drupal.org/project/oa_domains, https://www.drupal.org/node/2291719, https://www.drupal.org/node/2042191, https://www.drupal.org/node/2162997, https://www.drupal.org/node/2295921 I can not manage to set this up correctly.
I did the following but without the right results:
The result is that all pages within my OA2 are found on all subdomains, but not one of the subdomains lead to right space. I other words, node/1 which is in space1 is also available in space2.
Comment #4
Ed Carlevale commentedI used Open Atrium's Domains module on new sites I'm building and it worked like a charm (http://drupalgroup.mit.edu/ and http://mitenergyclub.org). I'm not sure why #1 is using the domain module in any case, as it seems to be a single website: http://somegroup.com. This is a simple standard configuration. If you purchased your domain name on GoDaddy, their help staff can walk you through these settings in a few minutes.
Pantheon has a nice help page on this, "Pantheon | Setting up a domain with Godaddy"
As for #3, all the bullet points look good except for the first one, "Created subdomains in my DNS pointing to my OA2 installation folder." I'm not sure what that means. If you look at the site I'm building now (http://drupalgroup.mit.edu/), you'll see three separate sites -- http://drupalgroup.mit.edu, http://horizontalgenius.com, and http://edcarlevale.com -- each of which is simply its own open atrium space.
Using the Domains module, I provided a base domain name (admin/openatrium/setting) for the entire site: drupalgroup.mit.edu. Then a domain name for each space:
1. mysite.com/drupalgroup (drupalgroup.mit.edu)
2. mysite.com/hg (horizontalgenius.com)
3. mysite.com/ec (edcarlevale.com)
Then I went into my GoDaddy account and pointed the DNS zones to where the sites are (on Pantheon). The domains were active virtually instantaneously.
Two final comments:
1. If you're working with a hosting platform like Pantheon with a dev, test and live environment, then don't set a global domain when you're in the dev or test environment. If you do, then every link will jump you over to the live environment, which will drive you crazy.
2. Pay some attention to the url patterns for the sections within a space. OA Domains handles this very nicely if you do. For example, if the original url is mysite.com/space1, then for Space1's blog go with a url like mysite.com/space1/blog. That way, the live site shows space1.com/blog/..., which is very helpful for keeping your site orderly.
Comment #5
hosais commentedThank you for the info. oa_domains works very well for me.
If you have problem about SSL setting, check my post https://www.drupal.org/node/2398353.
hosais
Comment #6
Argus commented#4: I see the 3 domains, but all content seems identical. Is your configuration still the way you described? The way I thought oa_domains would work is that all content should be seperate for each domain.
Comment #7
hosais commentedIn my configuration, the content is in the space. The space is separated from different domain. So that the content is separated from each domain.
however it is possible to see the space (in the wrong domain) in the menu if the user has both access to the two domains and the specific spaces, but when you click it, it will change to the domain of the space. Basically, this runs perfectly for me. Even better it is great if we would like to share the users in two domains.
hosais
Comment #8
hosais commentedHi
I have little issue related to the "front page" of the oa_domains.
the following is my test: (note: the orginal setup was only /domain1.com even it is only one domain)
domain1.com is basic domain. domain2.com is the space domain.
1) If I install (move) as /domain1.com/settings.php with symbolic link /domain2.com -> /domain1.com. The basic domain is domain1.com. The oa_home is only effective on domain1.com
That is:
the domain1.com -> oa_home page,
domain2.com -> domain2 space page
2) If I install (move) as /default/settings.php then oa_home is effective on both domains.
That is domain1.com -> oa_home page
domain2.com -> oa_home page
why? is there simple explanation about this? In this case, I even cannot go to the domain2 space anymore, since domain2 space=domain2.com = oa_home. So I need to type node/nid/edit or go to database to change the space page. I think this is not right.
I dont understand this. any help is appreciate.
hosais
Comment #9
Argus commentedCreated a documentation page.
@hosais; you better open a separate issue for that.
Comment #10
hosais commentedHi, FYI
I tested with a clean installation. no matter /default or /domains.com the result are the same.
the domain1.com -> oa_home page,
domain2.com -> domain2 space page
I know now that the correct behavior should be like this.
I dont know why my installation would have problem. Maybe because the /files location need to be original installation (because clean installation has nothing in the file directory so far). Anyway, this problem seems to not important currently.
hosais
Comment #12
hazit commentedThanks Argus for the excellent documentation page at https://www.drupal.org/node/2401483
I have OA domains up and working and so far its working great.
One thing I notice is that the page title (in the tab at the top of the browser page) still reads in the following format:
[node:title] | [site:name]
With domains it probably makes more sense for this to default to:
[node:title] | [space:name] or [node:title] | [domain:name]
I get that you can change the site name under OA config, but that changes it for everything, including any domains you have set up using the same base url.
I've spent quite a bit of time trying to find where I might change this
but could not figure it out.Modules recommended elsewhere for solving this problem include Metatag (https://www.drupal.org/project/metatag) and Page title (https://www.drupal.org/project/page_title). Metatag appears to have captured the functionality of Page title, but I'm reluctant to instal a new module every time I come across a problem like this.1) Have others found this to be a straightforward problem to solve using the existing modules in the OA distribution?2) Does it require additional module(s) to solve (ie Metatag);3) Should this be added as an issue for OA Domains; and/or4) Should we add something to How to set up OA Domains on this?(done - see below)Many thanks
Comment #13
hazit commentedScratch that - I found the solution while looking for something else.
You can customise the site name (which appears on your browser tabs) on a per-space basis by clicking the "gear" on the top right-hand side and selecting "Config" for each space. There you can edit the Site Name for each Space under "Variables".
This may be obvious for experienced users but can take a while for novice users to figure out.
I added a note to this effect at https://www.drupal.org/node/2401483.
Cheers
Comment #14
Argus commentedThanks hazit :)