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: > > > 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: > > <link rel="stylesheet" type="text/css" href="{{ MEDIA_URL }}css/ > > default.css" /> > > > But if there is an 500 error in the admin interface, it seems that > > MEDIA_URL is empty. > > ('django.core.context_processors.media' is activated in the > > settings.py file) > > I've been having this exact problem, but hadn't gotten around to > figuring out why. > > > Could this be a bug or is this expected behaviour? > > 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. > > -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---