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 f
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
On Jan 15, 9:34 am, Shev <[EMAIL PROTECTED]> wrote:
> Thanks for the feedback - I'm not seeing any traceback - just the
> vanilla "Internal Server Error" page that apache2 comes with,
> seemingly for all exceptions (e.g. failed import, bad template
> operation, bad logic in a view, etc. etc.) Whe
Thanks for the feedback - I'm not seeing any traceback - just the
vanilla "Internal Server Error" page that apache2 comes with,
seemingly for all exceptions (e.g. failed import, bad template
operation, bad logic in a view, etc. etc.) When I turn DEBUG = True
on in the settings, then the standard
On Jan 14, 2008 11:36 PM, Shev <[EMAIL PROTECTED]> wrote:
>
> Hi all - I'm using apache2 and mod_python (sitting behind nginx) and
> the latest trunk version of django, and have setup the 500.html error
> template as suggested. Unfortunately, it doesn't seem to work -
> whenever there's a problem
5 matches
Mail list logo
