Re: How to log the cause of a 500 error

On Nov 6, 2008, at 6:11 AM, Delta20 wrote: > > I just realized that I accidentally named the template 400.html not > 404.html... d'oh. I definitely need a better way of diagnosing 500 > errors. > > Thanks to the pointer to the email settings. I will set that up, but > I'm wondering if there's a

Re: How to log the cause of a 500 error

I just realized that I accidentally named the template 400.html not 404.html... d'oh. I definitely need a better way of diagnosing 500 errors. Thanks to the pointer to the email settings. I will set that up, but I'm wondering if there's a way to direct django to log those errors rather than email

Re: How to log the cause of a 500 error

> The problem I'm having right now is that I'm getting a 500 error > instead of 404s when Debug=False. I get 404s as expected when > Debug=True. I can't for the life of me figure out what is breaking, > since I don't have any error data to go off. Django sends you exception logs by mail if you se

How to log the cause of a 500 error

Is there a way to have django log 500 errors to a file, and otherwise log stderr/stdout to a file somewhere? The problem I'm having right now is that I'm getting a 500 error instead of 404s when Debug=False. I get 404s as expected when Debug=True. I can't for the life of me figure out what is bre