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 of the 500 error template, or possibly indicates another error in your application settings.
Ian
--
Regards,
Ian Clelland
<clelland@gmail.com>
-- On Tue, Feb 21, 2012 at 10:36 AM, rabousha <ramiaboushawish@gmail.com> wrote:
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 commas
are not added by default. All pages do exist, so I am not missing
anything.
Is this a known bug?
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Regards,
Ian Clelland
<clelland@gmail.com>
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment