Now my expectation (out of the box even) would be that the sub1-hostname can't be used to access sub2, sub3 or any other homenode.
But as it seems (even after following a lot of tips, including the above one)
I can still do sub1.domain.com/sub2 or sub9.domain.com/sub3 (or any other combination) and the content shows up.
Is there a way other then:
the above or adding urlProviderMode="absolute" in the web.routing in the umbracosettins.config that "locks" the startnodes to their respective hostnames?
Umbraco 8 - useDomainPrefixes Fails
Hi
We've just made a new website project with multiple websites instances.
Structure:
Website-1.com - Frontpage
Website-2.com - Frontpage
Website-3.com - Frontpage
We have made this kind of website projects before and used the Domain Prefix to make this possible inside the config/umbracosettings.config file:
But in the new Umbraco 8.x.x we are getting an weird error message:
If we change it to >false< we get the same error.
Our guess is that this setting has changed in Umbraco 8. But we cannot find any documentation on how to setup our project.
Any help would be appreciated :)
Cheers
Okay think i figured out the problem.
Umbraco 8 uses these lines in the web.config
instead of the useDomainPrefixes:
Hi Mads,
I´m trying to build multiple sites for the first time and I came across this problem. Did you manage to get it working? was this the solution?
Tried this, but I can still access the sites using eachothers url
I have several (9 to be exact) homenodes with their own hostnames
So lets call them
sub1.domain.com sub2.domain.com ... sub9.domain.com
Now my expectation (out of the box even) would be that the sub1-hostname can't be used to access sub2, sub3 or any other homenode.
But as it seems (even after following a lot of tips, including the above one)
I can still do sub1.domain.com/sub2 or sub9.domain.com/sub3 (or any other combination) and the content shows up.
Is there a way other then: the above or adding urlProviderMode="absolute" in the web.routing in the umbracosettins.config that "locks" the startnodes to their respective hostnames?
is working on a reply...