[patch] made media_url accessibly thru context_processor

[dummy@…]

I asked the users-list for a solution to access MEDIA_URL in templates. The simplest and general solution are 3 lines to make a own context_processor. Since this is a general issue for maybe a lot of others it comes in mind that is a possible feature for django.core.context_processors ?

[dummy@…]

django.core.content_processor.media_url

[Adrian Holovaty]

I'm marking this as a wontfix due to the slippery slope potential. If we added this, then people would want a context processor for another setting, and for another setting, and for another. We've already ruled out the idea of a "settings" context processor (see [1278]), so I'd recommend that people write their own two-line context processors if they really want this stuff.

[treborhudson@…]

I agree that this should be there by default. I can understand the slippery slope argument, but this makes sense. Other settings being viewable at the template level do not.

What's the point of setting MEDIA_URL if you can't use it in the templates? Where does it ever get used?

I can see that either a person is going to make their own context processor, or they're going to repeat themselves and list the absolute URL in their templates as well as in the settings (which violates the DRY principle).

I checked what the Django website does currently and it's confusing. In settings.py, MEDIA_URL is set to a broken URL:
MEDIA_URL = "​http://www.djangoproject.com.com/m/" # <- 2 .com's in there
But in the templates, it's hard coded as ​http://media.djangoproject.com/.

This makes me thing MEDIA_URL is useless. I'd much prefer setting it once and having an easy way to use it in the templates.

[Marc Fargas <telenieko@…>]

More on #1278 with patch, docs and so on...

[Marc Fargas <telenieko@…>]

Discussion on ​http://groups.google.com/group/django-developers/browse_thread/thread/8547935c231edf44/#