#1278: MEDIA_URL needs to be accessible from templates
----------------------+-----------------------------------------------------
Reporter: matt | Owner: adrian
Status: closed | Component: Template system
Version: SVN | Resolution: wontfix
Keywords: | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------+-----------------------------------------------------
Comment (by Simon Litchfield <[EMAIL PROTECTED]>):
Not talking about imagefields and the like here, this is for all your flat
files like css, logos/interface images, stock js's, etc. Hard-coding those
into templates doesn't make sense; the framework encourages pluggability
and separated delivery.
Anyway agreed the _constants idea is creep; _processors already handles
that.
Still think MEDIA_URL should be a core tag, or made available through a
default context_processor though, or something like that; so newbies in
particular are encouraged to use it straight up. Theres numerous blogs and
such out there showing workarounds, and plenty of queries have come in
over it...
--
Ticket URL: <http://code.djangoproject.com/ticket/1278#comment:17>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
