On Sep 8, 8:57 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > Because that's when Django is not going to use the debugging page, but > rather display your 500 template. When DEBUG=True, you will see the nice > debugging page, but that's for development purposes, not for general > production use (although it can be useful to have it on for brief > periods in production to diagnose problems).
I probably wasn't very clear. When DEBUG = True, the admin loads just fine. My problem is that I can't get the admin to fail when debugging is turned on, so I can never see the helpful Django debugging page. Further, I don't believe any objects are passed to the 500 template, so I can't display errors using my template. That's why I removed my 500.html template -- so that mod_python would throw the (nasty looking) error. I'm trying to figure out a) why the admin is throwing errors only when DEBUG=False and b) how I can display the source of the error. Thanks, Bret --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
