Karen,
The ticket says, "If flatpages and DEBUG=False and 404.html doesn't
exist it throws the error".
I have DEBUG=True, and I'm getting an "Unhandled Exception" error, not
the default yellow "Django 404 Error with DEBUG=True"
Anyways, the issue now seems to be with the way flatpages handles
On 12/5/07, Derek Payton <[EMAIL PROTECTED]> wrote:
>
>
> Apparently there was an issue with my svn. I downgraded to a previous
> revision (pre-6778), then back to trunk. Everything is working now,
> except flatpages. Here's the error from lighttpd's log:
> http://dpaste.com/26918/
>
> As per the
Apparently there was an issue with my svn. I downgraded to a previous
revision (pre-6778), then back to trunk. Everything is working now,
except flatpages. Here's the error from lighttpd's log: http://dpaste.com/26918/
As per the last line in the log, I created a (blank) 404.html in my
templates
Derek just noticed in IRC that [6895] is still failing on flatpages.
--~--~-~--~~~---~--~~
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
Chris,
[EMAIL PROTECTED]:~/django-trunk$ svn update
At revision 6897.
Any ideas?
Thank you,
--Derek
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
Sounds like this bug - http://code.djangoproject.com/ticket/6063
which was supposed to be fixed in [6895]. Are you sure you have the most
recent checkout?
-Chris
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hello,
I was recently charged with installing a new development server at
work, and I'm having some trouble getting Django to work as FastCGI
under Lighttpd. The new server is setup identical to the old server,
except for some hardware upgrades and we moved from Ubuntu Dapper to
Ubuntu Gutsy.
7 matches
Mail list logo
