The Home page under Site1 is the site homepage for site 1.
The Home page under Site2 is the site homepage for site 2.
The Site1 Home page has two domains names, bindings 1 & 2, i.e. site1a.local and site1b.local. Both domain names are added under "Manage Hostnames", each with the same language.
The Site2 Home page has two domains names, bindings 3 & 4, i.e. site2a.local and site2b.local. Both domain names are added under "Manage Hostnames", each with the same language.
Here's the problem: When I look at site1a.local, and have a link on the homepage (generated via NiceUrl) pointing to the child page Page1, I see http://site1b.local/page1/
Why is it displaying the other domain name in the URL?
I've tried clearing the cache but whichever domain name I use first, when I look at the other domain name, it contains URLs for the one I looked at first.
I have exactly the same problem on Site 2.
I do have umbracoHideTopLevelNodeFromPath = true (for obvious reasons), and also have useDomainPrefixes = true. So I thought I'd try setting useDomainPrefixes = false to make URLs relative, but guess what, that makes the top level node display in the URL: /home/page1/, even though umbracoHideTopLevelNodeFromPath is still true!
I know it's arguable for SEO purposes that one domain should 301 redirect to the other, but my customer wants both domains to function as though they are separate sites, and we already set the canonical URL for search engines anyway.
So, am I missing a trick here? Am I doing something wrong? Or is this a bug? Either way I could really do with a solution to this problem.
I've read lots of other posts that indicated similar things happening to them, e.g. "beneath level 3..." and to do with "multiple languages". Maybe it's all related.
Hi @Jamie. It's been a while since the original post. We ended up having to have one domain name per site and creating 301 URL redirects to it from the other domains. It wasn't ideal, but was a viable solution based on our customer's requirements.
That's not to say it hasn't since been addressed in a later version of Umbraco.
Multiple Hostnames Buggy?
I have two separate but related sites within one Umbraco installation (version 4.7.1.1), e.g.:
Content
>Site1
>>Home
>>>Page1
>Site2
>>Home
>>>Page1
In IIS I have four bindings:
The Home page under Site1 is the site homepage for site 1.
The Home page under Site2 is the site homepage for site 2.
The Site1 Home page has two domains names, bindings 1 & 2, i.e. site1a.local and site1b.local. Both domain names are added under "Manage Hostnames", each with the same language.
The Site2 Home page has two domains names, bindings 3 & 4, i.e. site2a.local and site2b.local. Both domain names are added under "Manage Hostnames", each with the same language.
Here's the problem: When I look at site1a.local, and have a link on the homepage (generated via NiceUrl) pointing to the child page Page1, I see http://site1b.local/page1/
Why is it displaying the other domain name in the URL?
I've tried clearing the cache but whichever domain name I use first, when I look at the other domain name, it contains URLs for the one I looked at first.
I have exactly the same problem on Site 2.
I do have umbracoHideTopLevelNodeFromPath = true (for obvious reasons), and also have
useDomainPrefixes = true. So I thought I'd try setting useDomainPrefixes = false to make URLs relative, but guess what, that makes the top level node display in the URL:
/home/page1/, even though umbracoHideTopLevelNodeFromPath is still true!
I know it's arguable for SEO purposes that one domain should 301 redirect to the other, but my customer wants both domains to function as though they are separate sites, and we already set the canonical URL for search engines anyway.
So, am I missing a trick here? Am I doing something wrong? Or is this a bug? Either way I could really do with a solution to this problem.
I've read lots of other posts that indicated similar things happening to them, e.g. "beneath level 3..." and to do with "multiple languages". Maybe it's all related.
Please advise!
Was a solution to this ever found?
Hi @Jamie. It's been a while since the original post. We ended up having to have one domain name per site and creating 301 URL redirects to it from the other domains. It wasn't ideal, but was a viable solution based on our customer's requirements.
That's not to say it hasn't since been addressed in a later version of Umbraco.
is working on a reply...