>Did I mention that it's the *PRODUCTION* environment? And I can't just >'activate DEBUG', I want the error to be logged whenever it happens >and.
With production environments, Django explicitely tries to _not_ send out informations to the users, as those might contain important stuff you don't want to tell someone outside. For production environments you usually set the DEFAULT_FROM_EMAIL and SERVER_EMAIL (one of those is used as the From: field for server emails, don't know which at the moment, presumeably it's SERVER_EMAIL, while the other is for password reminders and stuff like that) and ADMINS settings (ADMINS is set to a list of (name, email) tuples). That way the server sends out emails when an exception occurs. In the email you get informations on the exception and the traceback and stuff like that. The problem with the template discovery is usually not solved by that - you have to dig through the traceback to see wether you can deduct what template it was, or try to reproduce the template error in your development environment (I usually keep the dev environment around after making a site life - that way I can pull in a database dump from the production environment from time to time and reproduce errors on that dev server without needing to modify the production server). bye, Georg
