#10232: On development server, MEDIA_URL exists without setting
context_instance.
Works properly in mod_python.
---------------------------+------------------------------------------------
Reporter: chazmatazz | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.0
Keywords: | Stage: Unreviewed
Has_patch: 0 |
---------------------------+------------------------------------------------
'''Steps to repeat the problem:'''
1. In settings.py set TEMPLATE_CONTEXT_PROCESSORS to include
'django.core.context_processors.media'
2. In settings.py set MEDIA_URL to a non empty string e.g. '/media/'
3. In views.py, run render_to_response _without_ setting context_instance.
4. Have in the template used by render_to_response {{ MEDIA_URL }}
'''Expected:'''
{{ MEDIA_URL }} evaluates to '/media/'
'''What should happen'''
{{ MEDIA_URL }} evaluates to ''. This is what happens in mod_python.
'''Other notes'''
This is a bug in the development server. It's annoying because you think
you have a working setup in development, but then you go to deploy and
it's not working.
--
Ticket URL: <http://code.djangoproject.com/ticket/10232>
Django <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
-~----------~----~----~----~------~----~------~--~---
