Ive been using the uComponents multisite 404 handler which has been working perfectly on my local development machine. I've deployed to live but the 404 handler is no longer working.
Both environments are running on Windows Server 2008, IIS 7 with seemingly the same settings. Both are running in integrated mode.
Does anyone have any experience with this, or does anyone know why this might not be working on live?
thanks for your response. Im just gettting a standard IIS ugly 404, which as I say is very weird because on my development machine which has the same setup I get the 404 that I have chosen via the uComponent page picker.
Both servers are running windows 2008, custom errors are turned off.
@Lee, it was a coincidence I discovered that setting.
The site I am developing is still using WebForms rendering engine, so I am not sure whether changing the default setting from false to true could have a bad influence on MVC routing maybe. I haven't tested that scenario.
uComponents multisite 404
Hi all,
Ive been using the uComponents multisite 404 handler which has been working perfectly on my local development machine. I've deployed to live but the 404 handler is no longer working.
Both environments are running on Windows Server 2008, IIS 7 with seemingly the same settings. Both are running in integrated mode.
Does anyone have any experience with this, or does anyone know why this might not be working on live?
Thanks in advance
Al
Hi Al,
When you say that it is no longer working, what is happening instead? Are you getting a 404 page from IIS? or an Umbraco-generated 404 page?
Thanks, Lee.
Hi Lee,
thanks for your response. Im just gettting a standard IIS ugly 404, which as I say is very weird because on my development machine which has the same setup I get the 404 that I have chosen via the uComponent page picker.
Both servers are running windows 2008, custom errors are turned off.
Any help would be greatly appeeciated.
thanks
Al
Hi Al,
I've had this on a few websites, where IIS is keeping hold of the 404 errors.
Try adding this to your Web.config file, place it within the <system.webServer> section:
Cheers, Lee.
Hi Lee,
You're a legend - working like a treat!
Thanks for your help.
Regards,
Al
Hi all,
just a little notice. I spent a day on troubleshooting why none of the 404-handlers were triggered.
In the umbracoSettings.config, I found this section at the very bottom:
But trySkipIisCustomErrors MUST be set to true, so Umbraco doesn't route to IIS default 404-handler directly.
This setting was set to false in both Umbraco 6.1.2 and 6.1.3.
Hope this can help others.
Kind regards,
Kenneth Hein Møller
@Kenneth - thanks for raising that point (I wasn't aware of that config setting).
Seems that it is set to 'false' by default for backwards compatibility reasons - but I believe that it will be set to 'true' in v7+
Cheers, Lee.
@Lee, it was a coincidence I discovered that setting.
The site I am developing is still using WebForms rendering engine, so I am not sure whether changing the default setting from false to true could have a bad influence on MVC routing maybe. I haven't tested that scenario.
Kind regards
Kenneth Hein Møller
Sorry for digging this old thread up again, but I feel the need to do more than high-5-you-rock to show how happy I am!
I searched FOR EVER for a solution for this, always just letting it be after a few hours of unsuccessful research and trying.
Thanks!
@Jan Brinker, I am glad it was helpful to you :)
Hopefully this will be the standard from v7 and onwards, as @Lee mentions.
is working on a reply...