Loading django/contrib/admin/sites.py +2 −2 Original line number Diff line number Diff line Loading @@ -174,8 +174,8 @@ class AdminSite(object): raise ImproperlyConfigured("Put 'django.contrib.contenttypes' in " "your INSTALLED_APPS setting in order to use the admin application.") if 'django.contrib.auth.context_processors.auth' not in Engine.get_default().context_processors: raise ImproperlyConfigured("Put 'django.contrib.auth.context_processors.auth' " "in your TEMPLATE_CONTEXT_PROCESSORS setting in order to use the admin application.") raise ImproperlyConfigured("Enable 'django.contrib.auth.context_processors.auth' " "in your TEMPLATES setting in order to use the admin application.") def admin_view(self, view, cacheable=False): """ Loading django/template/context.py +1 −1 Original line number Diff line number Diff line Loading @@ -187,7 +187,7 @@ class RenderContext(BaseContext): class RequestContext(Context): """ This subclass of template.Context automatically populates itself using the processors defined in TEMPLATE_CONTEXT_PROCESSORS. the processors defined in the engine's configuration. Additional processors can be specified as a list of callables using the "processors" keyword argument. """ Loading django/template/context_processors.py +3 −2 Original line number Diff line number Diff line Loading @@ -3,9 +3,10 @@ A set of request processors that return dictionaries to be merged into a template context. Each function takes the request object as its only parameter and returns a dictionary to add to the context. These are referenced from the setting TEMPLATE_CONTEXT_PROCESSORS and used by RequestContext. These are referenced from the 'context_processors' option of the configuration of a DjangoTemplates backend and used by RequestContext. """ from __future__ import unicode_literals from django.conf import settings Loading docs/internals/deprecation.txt +1 −0 Original line number Diff line number Diff line Loading @@ -90,6 +90,7 @@ details on these changes. * The following settings will be removed: * ``ALLOWED_INCLUDE_ROOTS`` * ``TEMPLATE_CONTEXT_PROCESSORS`` * ``TEMPLATE_DIRS`` * ``TEMPLATE_LOADERS`` * ``TEMPLATE_STRING_IF_INVALID`` Loading docs/ref/class-based-views/mixins-simple.txt +4 −5 Original line number Diff line number Diff line Loading @@ -61,11 +61,10 @@ TemplateResponseMixin .. versionchanged:: 1.8 In older versions of Django, ``TemplateResponse`` used :class:`~django.template.RequestContext` in such a way that callables defined in :setting:`TEMPLATE_CONTEXT_PROCESSORS` would override template variables defined in your views. For example, if you subclassed :class:`DetailView <django.views.generic.detail.DetailView>` and :class:`~django.template.RequestContext` in such a way that values from template context processors would override template variables defined in your views. For example, if you subclassed :class:`DetailView <django.views.generic.detail.DetailView>` and set ``context_object_name`` to ``user``, the ``django.contrib.auth.context_processors.auth`` context processor would overwrite your variable with the current user. Now, for Loading Loading
django/contrib/admin/sites.py +2 −2 Original line number Diff line number Diff line Loading @@ -174,8 +174,8 @@ class AdminSite(object): raise ImproperlyConfigured("Put 'django.contrib.contenttypes' in " "your INSTALLED_APPS setting in order to use the admin application.") if 'django.contrib.auth.context_processors.auth' not in Engine.get_default().context_processors: raise ImproperlyConfigured("Put 'django.contrib.auth.context_processors.auth' " "in your TEMPLATE_CONTEXT_PROCESSORS setting in order to use the admin application.") raise ImproperlyConfigured("Enable 'django.contrib.auth.context_processors.auth' " "in your TEMPLATES setting in order to use the admin application.") def admin_view(self, view, cacheable=False): """ Loading
django/template/context.py +1 −1 Original line number Diff line number Diff line Loading @@ -187,7 +187,7 @@ class RenderContext(BaseContext): class RequestContext(Context): """ This subclass of template.Context automatically populates itself using the processors defined in TEMPLATE_CONTEXT_PROCESSORS. the processors defined in the engine's configuration. Additional processors can be specified as a list of callables using the "processors" keyword argument. """ Loading
django/template/context_processors.py +3 −2 Original line number Diff line number Diff line Loading @@ -3,9 +3,10 @@ A set of request processors that return dictionaries to be merged into a template context. Each function takes the request object as its only parameter and returns a dictionary to add to the context. These are referenced from the setting TEMPLATE_CONTEXT_PROCESSORS and used by RequestContext. These are referenced from the 'context_processors' option of the configuration of a DjangoTemplates backend and used by RequestContext. """ from __future__ import unicode_literals from django.conf import settings Loading
docs/internals/deprecation.txt +1 −0 Original line number Diff line number Diff line Loading @@ -90,6 +90,7 @@ details on these changes. * The following settings will be removed: * ``ALLOWED_INCLUDE_ROOTS`` * ``TEMPLATE_CONTEXT_PROCESSORS`` * ``TEMPLATE_DIRS`` * ``TEMPLATE_LOADERS`` * ``TEMPLATE_STRING_IF_INVALID`` Loading
docs/ref/class-based-views/mixins-simple.txt +4 −5 Original line number Diff line number Diff line Loading @@ -61,11 +61,10 @@ TemplateResponseMixin .. versionchanged:: 1.8 In older versions of Django, ``TemplateResponse`` used :class:`~django.template.RequestContext` in such a way that callables defined in :setting:`TEMPLATE_CONTEXT_PROCESSORS` would override template variables defined in your views. For example, if you subclassed :class:`DetailView <django.views.generic.detail.DetailView>` and :class:`~django.template.RequestContext` in such a way that values from template context processors would override template variables defined in your views. For example, if you subclassed :class:`DetailView <django.views.generic.detail.DetailView>` and set ``context_object_name`` to ``user``, the ``django.contrib.auth.context_processors.auth`` context processor would overwrite your variable with the current user. Now, for Loading