I'm trying to get a single instance of umbraco to host two (eventually more) sites. I have an issue where content published in the second site appears published from the umbraco backend, but is not available on the site. i.e. if I follow the "Link to document" link from the backend then I get a 404. I have reproduced my issue with a straight up vanilla install.
New ASP.NET Empty Web Application from Visual Studio 2013
Used nuget to install Umbraco 7.1.1
Used customized option in the Umbraco wizard to select a fresh SQL Server database.
In hosts file set site1.net and site2,net to point to 127.0.0.1
In IIS created two new web sites pointing to my Umbraco folder on disk, using a different new app pool for each and with the appropriate site1.net or site2.net binding.
In the Umbraco backend, created a "Master" doc type, and a child "Basic Page" doc type.
Under Content, create two Master instances.
Set one to site1.net and the other site2.net under Culture And Hostnames
In Umbraco web.config set useDomainPrefixes to true.
Create some Basic Page instances under site1 and site2. All pages show the correct url under "Link to Document", however most times (although not every single time) when I follow the link on site2 I get a 404 error. If I refresh the app pool for site2 then the published content is accesible. This makes me think the issue is to do with Umbraco caching the published content. If I do the same on site1 the link always works first time. The only difference between the two Master nodes is that site1 is first in the list.
As this seems a fairly simple and common scenario I suspect I have set something up incorrectly, however after banging my head against this problem for several hours I'm struggling to work it out myself.
This could potentially be a bug and I think it should be reported at the issue trakcer.
When you edit a page on site2.net - Are you then logged into Umbraco using site2.net/umbraco or do you do it from site1.net/umbraco? That could perhaps have something to do with it...But I think a bug report would be the right thing to do.
Multiple hostname setup issue
Hi,
I'm trying to get a single instance of umbraco to host two (eventually more) sites. I have an issue where content published in the second site appears published from the umbraco backend, but is not available on the site. i.e. if I follow the "Link to document" link from the backend then I get a 404. I have reproduced my issue with a straight up vanilla install.
Create some Basic Page instances under site1 and site2. All pages show the correct url under "Link to Document", however most times (although not every single time) when I follow the link on site2 I get a 404 error. If I refresh the app pool for site2 then the published content is accesible. This makes me think the issue is to do with Umbraco caching the published content. If I do the same on site1 the link always works first time. The only difference between the two Master nodes is that site1 is first in the list.
As this seems a fairly simple and common scenario I suspect I have set something up incorrectly, however after banging my head against this problem for several hours I'm struggling to work it out myself.
Any help would be much appreciated. Thanks.
Hi Tom
This could potentially be a bug and I think it should be reported at the issue trakcer.
When you edit a page on site2.net - Are you then logged into Umbraco using site2.net/umbraco or do you do it from site1.net/umbraco? That could perhaps have something to do with it...But I think a bug report would be the right thing to do.
/Jan
Thanks for your quick response.
Yes, that does appear to help. I was publishing the pages from site1.
I can confirm the opposite problem occurs if I publish site1 pages from the site2 backend.
I will submit a bug
is working on a reply...