On Tue, Jun 9, 2009 at 4:51 PM, joshm <joshmat...@gmail.com> wrote: > > Here is a link to a screenshot of the traceback, unfortunately I don't > have more than that for right now... > > http://img25.imageshack.us/img25/8711/tracem.png >
This is happening on your production server, and you have DEBUG set to True so are relying on notification/screenshots from your users to know when something goes wrong? That's a really bad setup, for many reasons. The one you are hitting now is you don't get information on the error. If you had DEBUG set to False, appropriate settings for ADMINS: http://docs.djangoproject.com/en/dev/ref/settings/#admins and possibly various EMAIL_XXXX settings so that the Django code can successfully send emails, you would have the full traceback mailed to you when an error occurs. That screenshot doesn't help because it's not the complete traceback. If your user would click the "switch to copy and paste view" link and then copy and paste the full traceback and mail it to you that might provide a clue. But really you shouldn't be exposing debug pages to general users.... Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
