Now I expect this again is going to be defended religiously; but the
fact that 500's don't run context processors, to me, serves as a nice
little reminder that {% media_url %} or similar needs to be a core
template tag. Where is the sense in bothering with a custom 500 if you
can't conveniently use css, images, etc?On Nov 10, 5:40 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Nov 9, 2007 1:29 PM, Brot <[EMAIL PROTECTED]> wrote: > > > does this mean, that there is no solution for this problem or is there > > a smart workaround? > > This means there is absolutely nothing in Django which will, in the > server error view, attempt to run yourcontextprocessors. There is > not a switch you can flip or a button you can press or an argument you > can pass or a setting you can change to affect this: Django assumes > that when things break badly enough to result in a500, it's not safe > to rely on anything at all being in working condition. > > If you want to specify a different handler for 500s, that's up to you, > but be prepared for the inevitable complete breaking of your site when > something running inside it raises another exception. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
