Re: setting DEBUG=False disables flatpages

On Tue, Jun 8, 2010 at 2:56 PM, adrian wrote: > tracked the problem more down... > > the problem appeared when using own handler404/handler500 views and > returning the invalid HttpResponse instead of HttpResponseNotFound/ > HttpResponseServerError. This is not

Re: setting DEBUG=False disables flatpages

You need to have a 500.html and a 404.html defined when DEBUG=False. See: http://code.djangoproject.com/ticket/3335 Hope this helps! Dan Harris dih0...@gmail.com On Jun 8, 2:56 pm, adrian wrote: > tracked the problem more down... > > the problem appeared when using

Re: setting DEBUG=False disables flatpages

tracked the problem more down... the problem appeared when using own handler404/handler500 views and returning the invalid HttpResponse instead of HttpResponseNotFound/ HttpResponseServerError. This is not documented and needs doc improvement ... -- You received this message because you are

Re: setting DEBUG=False disables flatpages

On 8/06/2010 4:58pm, adrian wrote: Hello Guys, on all my projects I have the problem that setting DEBUG=False in settings.py disables flatpages (404 Pages are displayed). This also applies to newly created projects. This happens with Django version 1.2.1. Can someone confirm this with his

setting DEBUG=False disables flatpages

Hello Guys, on all my projects I have the problem that setting DEBUG=False in settings.py disables flatpages (404 Pages are displayed). This also applies to newly created projects. This happens with Django version 1.2.1. Can someone confirm this with his deployments? Additionally if running the