On Jan 15, 2008 12:52 PM, Shev <[EMAIL PROTECTED]> wrote:
> On Jan 15, 10:05 am, Karen Tracey <[EMAIL PROTECTED]> wrote:
> > Then you need to check the apache error log, the traceback should be
> > included there.
>
> What should I be looking for? The tracebacks are there in the log,
> but I've found it never provides the useful and accurate information
> that the Django debugging page does; the only way I can effectively
> debug is to see what Django thinks is wrong. Thanks!
>
Bare tracebacks provide more limited information than a Django debug page,
but they're still accurate and informative, since they still tell you the
sequence of calls that led to the error. If you're having trouble making
sense of what's in the log someone from the list may be able to help if you
post the information. I suspect copy/pasting it from the log to an email
might mangle it rather badly, so posting it to someplace like dpaste.com and
then providing a pointer to it on the list might be best.
As for what to be looking for, if it's a case of Django not finding the
500.html, you should see something like:
raise TemplateDoesNotExist, name
TemplateDoesNotExist: 500.html
at the end of the traceback in the log. If that's not the problem, it'll be
something else...but without seeing what's actually in the log it's hard for
me to guess what it might be.
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
