Re: django 1.1: nonexistent URLs display 500.html instead of 404.html

On Tue, Feb 21, 2012 at 5:33 PM, rabousha wrote: > Yes, only for TEMPLATE_CONTEXT_PROCESSORS, the commas aren't added by > default after the strings. I suspect it's an old bug. > > TEMPLATE_CONTEXT_PROCESSORS = ( >'django.core.context_processors.auth' >

Re: django 1.1: nonexistent URLs display 500.html instead of 404.html

Yes, only for TEMPLATE_CONTEXT_PROCESSORS, the commas aren't added by default after the strings. I suspect it's an old bug. TEMPLATE_CONTEXT_PROCESSORS = ( 'django.core.context_processors.auth' 'django.core.context_processors.debug' 'django.core.context_processors.i18n'

Re: django 1.1: nonexistent URLs display 500.html instead of 404.html

By 'missing commas', do you mean that there are *syntax errors* in your settings.py file? That will definitely cause a 500 error, and I would be surprised if it didn't do it on *every* request. It seems odd that you would get a 404 when Debug is turned on, but that may be related to the handling

django 1.1: nonexistent URLs display 500.html instead of 404.html

I am using django 1.1, with DEBUG = False, and TEMPLATE_CONTEXT_PROCESSORS is missing commas, all nonexistent URLs display 500.html instead of 404.html. If I set DEBUG to True, it displays the default 404 page. if I add the commas to TEMPLATE_CONTEXT_PROCESSORS, then it displays the 404 page. The