On Mon, Jun 15, 2009 at 2:00 PM, Joseph Brown <joseb...@gmail.com> wrote:
> Well I'm flummoxed. After reading your post I retested on my dev site, and > the problem has vanished. Then I tried on production and same thing, it's > gone! > > I do have custom 404 and 500 templates. All I can figure that might have > changed is the file ownership - I'm using subversion and might have copied > the files from the repository incorrectly, I don't know, but that's all I > can think of that might have changed. > > The server is Apache2.2, urls.py has no handler for Flatpages, I just use > the fallback default in settings.py. > > Sorry if this is stupid, but since I'm rendering my 500 page for this > error, what's the best way to capture the traceback, if it happens again? > > Thanks for the help! > Short of placing logging around your system, Django has the ability to send e-mails with errors that include the traceback. Here is the documents regarding that: http://docs.djangoproject.com/en/dev/howto/error-reporting/#howto-error-reporting Hope that helps, Michael --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
