On Thu, Nov 19, 2009 at 1:08 AM, Graham Dumpleton < graham.dumple...@gmail.com> wrote:
> > > On Nov 19, 10:48 am, Alessandro Ronchi <alessandro.ron...@soasi.com> > wrote: > > With mod_wsgi I only get error logged into apache and not on the > interactive > > trackback in the browser, also If i set DEBUG=True in my settings. > > > > Is there any way to handle the django trackback as usual? > > Is the error definitely from Django and if so from what part of > Django? > > Perhaps post example of traceback. > > Have you looked at 'DEBUG_PROPAGATE_EXCEPTIONS' setting. > > > http://docs.djangoproject.com/en/dev/ref/settings/#debug-propagate-exceptions > > Also check over comments against: > > http://docs.djangoproject.com/en/dev/ref/settings/#debug > > and when tracebacks may be suppressed. > http://dpaste.com/122205/ is my log file. I don't used DEBUG_PROPAGATE_EXCEPTIONS but as far as I understand it defaults to False, so Django should handle the error with usual trackback, also with mod_wsgi? this is my vhost.conf (i'm using plesk): http://dpaste.com/122208/ and this is my wsgi app: http://dpaste.com/122209/ -- Alessandro Ronchi SOASI Sviluppo Software e Sistemi Open Source http://www.soasi.com http://www.linkedin.com/in/ronchialessandro -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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=.
