On Sun, 2007-11-11 at 16:51 -0800, sime wrote:
> 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
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 us
On Nov 9, 2007 2:40 PM, James Bennett <[EMAIL PROTECTED]> wrote:
> 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.
I think I'll settle for hardco
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 your context processors. There is
not a swit
does this mean, that there is no solution for this problem or is there
a smart workaround?
I think I could use a custom templatetag. But this would violate DRY.
Regards
Bernd
On Nov 9, 7:49 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> On Nov 9, 2007 12:34 PM, Brot <[EMAIL PROTECTED]> wrote
On Nov 9, 2007 12:49 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I seem to remember something a while back about 500 not processing too
> much, to reduce the possibility of getting into a recursive loop of
> exceptions. I can't seem to find that now, but that could be what
> we're running into.
On Nov 9, 2007 12:34 PM, Brot <[EMAIL PROTECTED]> wrote:
> I have defined a 500.html template in my root template directory.
> This template "extends" from my base.html template. In the base
> template I have something like:
>
>
> But if there is an 500 error in the admin interface, it seems th
Hello,
I have defined a 500.html template in my root template directory.
This template "extends" from my base.html template. In the base
template I have something like:
But if there is an 500 error in the admin interface, it seems that
MEDIA_URL is empty.
('django.core.context_processors.medi
8 matches
Mail list logo
