Last post Dec 16, 2005 10:10 AM by TimGT
Dec 13, 2005 03:15 PM|TimGT|LINK
Everytime a module on my DNN 3.2 site gets an error, it automatically gives the whole "Server Error in /" page. Didn't DNN use to display errors in the actual module instead of erroring the whle entire page?
If so, what happened to it? Can I check something to figure out why tiny module errors cause the whole DNN page to error out?
Dec 14, 2005 06:58 PM|cathal|LINK
Check the value of the <customErrors mode="" /> node in your web.config. If it's remoteonly, then it will only show the whole page error for the local machine, whereas remote users will get the custom error messages. Also log in as host, and make sure you've
checked the custom errors checkbox in host->host settings.
Dec 16, 2005 10:10 AM|TimGT|LINK
Thanks for the response!
That only shows the big error message which is not really what is in question.
My question is this: Why is it that suddenly when a module has any tiny error, the whole page goes into application error instead of the module simply having an error? It used to be that you'd get an "error loading module" but the rest of the page would
load. Now the entire page never loads.