It works now. That's because a typo error happens in my 404.html page. And it introduces 500.Thanks all.
On Tue, May 5, 2009 at 9:17 AM, Ronghui Yu <stone...@gmail.com> wrote: > Yes, 404.html and 500.html are there. But they extend from base.html, which > depends on some context variables. I will change them to a simple one and > see if the problem still there.Thanks > > > On Tue, May 5, 2009 at 12:06 AM, Brian Neal <bgn...@gmail.com> wrote: > >> >> On May 4, 10:28 am, Ronghui Yu <stone...@gmail.com> wrote: >> > Hi,All, >> > >> > I am going to use Flatpages app for those simple pages. And everything >> > works fine when settings.DEBUG is True, but when it is turned to False, >> > a URL not configured in urlpatterns will trigger 500, not 404. >> >> Do you have a 404.html error template? You need to have that before >> flatpages will work when DEBUG is False. See the note titled "Ensure >> that your 404 template works" in this section: >> >> >> http://docs.djangoproject.com/en/dev/ref/contrib/flatpages/#module-django.contrib.flatpages >> >> Its also a good idea to have a 500.html error template. >> >> Best, >> BN >> >> >> >> >> > > > -- > =========================== > Regards > Ronghui Yu > -- =========================== Regards Ronghui Yu --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
