id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
10232	On development server, MEDIA_URL exists without setting context_instance. Works properly in mod_python.	chazmatazz	nobody	"'''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."		closed	Uncategorized	1.0		worksforme			Unreviewed	0	0	0	0	0	0