Ok it looks like you can only use the customerrors not the additional httperrors in web.config so having a 500 page when the db cannot connect will not work properly.
also don't worry about doing anything in the umbracoconfig regarding errors as this will be ignored in favour of icontentlastchancefinder.
and place the error-500.html file in the site root folder, i tested it by changing the database name in web config to a non existent database and I get my html error page.
implementing 500 page stops IContentLastChanceFinder from working
I have just implemented a 500 error page using the web.config, however it stops my IContentLastChanceFinder from functioning.
How do we use these together?
Hi Damien,
500 errors are not connected to "IContentLastChanceFinder "
Content finder errors are 4xx
Thanks, Alex
Ok it looks like you can only use the customerrors not the additional httperrors in web.config so having a 500 page when the db cannot connect will not work properly.
also don't worry about doing anything in the umbracoconfig regarding errors as this will be ignored in favour of icontentlastchancefinder.
This works for me in the web.config
and place the error-500.html file in the site root folder, i tested it by changing the database name in web config to a non existent database and I get my html error page.
is working on a reply...