On Thu, Sep 3, 2009 at 4:27 AM, Alessandro <alessandro.ron...@gmail.com>wrote:
> 2009/9/1 Karen Tracey <kmtra...@gmail.com> > >> On Tue, Sep 1, 2009 at 12:02 PM, Alessandro Ronchi < >> alessandro.ron...@soasi.com> wrote: >> >>> When I return a 500 error I need to have my context_processor, in which I >>> store some important vars used in my template. Is it possible? >>> >> >> Your subject line says 404 errors but your text says 500. Which are you >> asking about? >> >> > sorry, the problem is on 500 errors. on 404 the context is correct (i've > tried). > > The default handler for 500s intentionally uses an empty Context for rendering, so as to minimize chances of another critical error being encountered. There was a period of 2 days 3 years ago where it used a RequestContext, but that was reconsidered to be a Bad Idea. Since then requests to change this have been rejected, see: http://code.djangoproject.com/ticket/5617 Here's a mailing list thread discussing it: http://groups.google.com/group/django-users/browse_thread/thread/aee94039eccf2d90/01fa9a19cd3350bc So, if you want to have your context processor run for 500s, you will have to provide your own custom 500 handler that uses a RequestContext. 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
