I am trying to work out how to host multiple sites on one instance of Umbraco, which is hosted on Azure. I've added the second domain as a custom domain on the Azure Web App. I've created two Home pages at the root of my Umbraco and set each to the appropriate hostname in 'Culture and Hostnames'. I can still navigate to the original site, but when I try to go to the second site I get the following error:
The call is ambiguous between the following methods or properties: 'Umbraco.Web.UmbracoHelper.Media(params int[])' and 'Umbraco.Web.UmbracoHelper.Media(params string[])'
No offending source code is identified.
I don't really know what I'm doing with this and try as I might I can't find any answers by googling the issue. Can anyone help?
Were you able to find a solution? Is a multi-site Umbraco installation possible in a Web App?
We're considering going down this route and I assume it's possible. But so far the posts I've read on how to do it involve IIS configuration, which isn't possible in a Web App.
It is possible. If I remember correctly, I had done the right things, but there was just a problem with the template or the document type (I can't remember exactly how I solved it, it was a while ago now). But basically, I think all I had to do was add a custom domain on the Web App and then put the right info in the Culture & Hostnames setting on the different home pages. I now have three sites running off the same Web App, two of which share the same template and one of which has its own. Hope that helps.
Thanks for getting back. My main concern was to confirm it's possible to create a multi-site installation in an Azure Web App. You just did, thank you!
Hi, Alistair,
Usually I get this error when I try Umbraco.Media(imgId) and imgId is null or empty string. Can you check if all the images are fine on the second site? Do you make null checks on the image fields?
One instance, multiple sites, on Azure - problems.
Hi,
I am trying to work out how to host multiple sites on one instance of Umbraco, which is hosted on Azure. I've added the second domain as a custom domain on the Azure Web App. I've created two Home pages at the root of my Umbraco and set each to the appropriate hostname in 'Culture and Hostnames'. I can still navigate to the original site, but when I try to go to the second site I get the following error:
The call is ambiguous between the following methods or properties: 'Umbraco.Web.UmbracoHelper.Media(params int[])' and 'Umbraco.Web.UmbracoHelper.Media(params string[])'
No offending source code is identified.
I don't really know what I'm doing with this and try as I might I can't find any answers by googling the issue. Can anyone help?
Thanks, Alistair
Were you able to find a solution? Is a multi-site Umbraco installation possible in a Web App?
We're considering going down this route and I assume it's possible. But so far the posts I've read on how to do it involve IIS configuration, which isn't possible in a Web App.
Hi Jon.
It is possible. If I remember correctly, I had done the right things, but there was just a problem with the template or the document type (I can't remember exactly how I solved it, it was a while ago now). But basically, I think all I had to do was add a custom domain on the Web App and then put the right info in the Culture & Hostnames setting on the different home pages. I now have three sites running off the same Web App, two of which share the same template and one of which has its own. Hope that helps.
Cheers, Alistair
Alistair,
Thanks for getting back. My main concern was to confirm it's possible to create a multi-site installation in an Azure Web App. You just did, thank you!
No problem, Jon. Good luck.
Hi, Alistair, Usually I get this error when I try Umbraco.Media(imgId) and imgId is null or empty string. Can you check if all the images are fine on the second site? Do you make null checks on the image fields?
Regards Mila
Hi Mila,
Thanks for the reply. That might have been the problem, but to be honest it is so long ago, I can't actually remember.
Cheers, Alistair
is working on a reply...