Fixed #18642 - Added a note suggesting the use of render() rather than render_to_response() if you need RequestContext in your template.
This commit is contained in:
parent
70896386ec
commit
f99ecaff06
|
@ -424,6 +424,10 @@ optional, third positional argument, ``processors``. In this example, the
|
||||||
my_data_dictionary,
|
my_data_dictionary,
|
||||||
context_instance=RequestContext(request))
|
context_instance=RequestContext(request))
|
||||||
|
|
||||||
|
Alternatively, use the :meth:`~django.shortcuts.render()` shortcut which is
|
||||||
|
the same as a call to :func:`~django.shortcuts.render_to_response()` with a
|
||||||
|
context_instance argument that forces the use of a ``RequestContext``.
|
||||||
|
|
||||||
Here's what each of the default processors does:
|
Here's what each of the default processors does:
|
||||||
|
|
||||||
django.contrib.auth.context_processors.auth
|
django.contrib.auth.context_processors.auth
|
||||||
|
|
Loading…
Reference in New Issue