etc... BUT if I try to browse from either mydomain1.co.uk or the other then I get a 404 and the shared page won't show. However.
If I add another domain to my bindings (i.e. mydomain3.co.uk) in IIS and don't set the hostname on Site On or Site Two. I can now browse to /repository/shared-page perfectly fine and see it?
Because hostname mydomain1.co.uk is set on Site One then the new pipeline looks for pages exclusively under that node. In the past, it did not work that way, but the end result was that it was possible to show pages of one site when displaying another site, expecially in case of 404... there are a few threads on Our discussing that.
The preferred solution now seem to be to set domains mydomain1.co.uk/repository and mydomain2.co.uk/repository on Repository. Because we do "greedy" matching, these will be considered before Site One and Site Two in case of urls starting with /repository.
Unable To Access Shared Nodes When Hostname Is Added
I think I have found a bug when you use hostnames and have a multi-site setup (running version 4.11.4). I have this structure in the Umbraco backend
- Site One (Hostname: mydomain1.co.uk)
-- Sub pages etc..
- Site Two (Hostname: mydomain2.co.uk)
-- Sub pages etc..
- Repository (No hostnames set)
--- Shared page
If I browse to the Repository > Shared Page. I can see on the properties tab that it has links like this
/repository/shared-page
mydomain1.co.uk/repository/shared-page
etc... BUT if I try to browse from either mydomain1.co.uk or the other then I get a 404 and the shared page won't show. However.
If I add another domain to my bindings (i.e. mydomain3.co.uk) in IIS and don't set the hostname on Site On or Site Two. I can now browse to /repository/shared-page perfectly fine and see it?
Anyone else had an issue like this?
It's not a bug, it's a feature ;-)
Because hostname mydomain1.co.uk is set on Site One then the new pipeline looks for pages exclusively under that node. In the past, it did not work that way, but the end result was that it was possible to show pages of one site when displaying another site, expecially in case of 404... there are a few threads on Our discussing that.
The preferred solution now seem to be to set domains mydomain1.co.uk/repository and mydomain2.co.uk/repository on Repository. Because we do "greedy" matching, these will be considered before Site One and Site Two in case of urls starting with /repository.
See what I mean?
is working on a reply...