I believe that the last e-mail was spam. Anyway django can send you an email whenever there is an error: http://www.djangoproject.com/documentation/settings/#error-reporting-via-e-mailThis is very helpful. Of course you need all the settings set up right and an e-mail server on your server or elsewhere. I also seem to remember a django snippet middleware not too long ago that took those errors and wrote them to a file if you didn't/couldn't want the email. I can't seem to find it right now though.
Hope that helps, Michael On Thu, Apr 10, 2008 at 3:05 PM, mustapha aymen <[EMAIL PROTECTED]> wrote: > http://ccpdz.sarl.tk > > 2008/4/10, Hancock, David (dhancock) <[EMAIL PROTECTED]>: > > > We've got a Django system deployed, and we set DEBUG=False in the > > settings file. What I'd still like to be able to do, though, is get the full > > traceback for viewing if needed. (The one that shows up with DEBUG=True.) > > > > The expandible/collapsible parts, local variables, etc., are helpful for > > troubleshooting, but I don't want the whole world to see them, of course. In > > another framework we use (Webware for Python), the fancy tracebacks get > > saved to disk, and we can view them securely. > > > > Do I need (to write) special middleware for this? Is there a solution > > I'm overlooking? > > > > Cheers! > > -- > > David Hancock | [EMAIL PROTECTED] > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
