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 500's. Not sure if it's a bug nor not. --Derek On Dec 5, 4:42 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > 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 last line in the log, I created a (blank) 404.html in my > > templates directory, and it seemed to fix it. > > > However, is this the intended behavior (requiring a 404.html for > > flatpages to work)? Should this be filed as a bug? > > You need to provide a 404.html independent of whether you are using > flatpages. Users can enter whatever they like in a browser address bar, > your site should respond with a sensible error message when they try to get > to a page that doesn't exist. > > http://code.djangoproject.com/ticket/3335 > > raised the issue of flatpages needing 404.html and was closed wontfix, so > I'd say the current behavior is intended. > > 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 -~----------~----~----~----~------~----~------~--~---
