[Answered ]-How to use {{ request.path }} in django 1.7.7

by

2đź‘Ť

âś…

Remove the :

"OPTIONS": {
        "debug": DEBUG,
        "context_processors": [
            "django.contrib.auth.context_processors.auth",
            "django.core.context_processors.debug",
            "django.core.context_processors.i18n",
            "django.core.context_processors.media",
            "django.core.context_processors.static",
            "django.core.context_processors.tz",
            "django.core.context_processors.request",
            "django.contrib.messages.context_processors.messages",
            "pinax_theme_bootstrap.context_processors.theme",
        ],
    },

Add :

TEMPLATE_CONTEXT_PROCESSORS = (
"django.contrib.auth.context_processors.auth",
"django.core.context_processors.debug",
"django.core.context_processors.i18n",
"django.core.context_processors.media",
"django.core.context_processors.static",
"django.core.context_processors.tz",
"django.contrib.messages.context_processors.messages"
"django.core.context_processors.request",
)

Nowhere in the documentation 1.7, they mention the “OPTIONS”, only in the doc 1.8,

If you aren’t rendering the request, like docs says:

If you’re using Django’s render_to_response() shortcut to populate a
template with the contents of a dictionary, your template will be
passed a Context instance by default (not a RequestContext). To use a
RequestContext in your template rendering, use the render() shortcut
which is the same as a call to render_to_response() with a
context_instance argument that forces the use of a RequestContext.

Maybe the problem is on yours views. try to use render instead of render_to_response (if you use it)

👤Paulo Pessoa

Leave a comment