innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

[2.1.x] Emphasized that TemplatesSetting must be used to override widget templates. 

Backport of 25f4302349 from master
This commit is contained in:
Stephen Finucane 2018-09-11 13:14:53 -06:00 committed by Tim Graham
parent 5bbcf83fce
commit 9c88826ff9
2 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/howto/overriding-templates.txt
View File

@ -12,6 +12,11 @@ the default Django template loader will try to load the template from the
project-level directory first. In other words, :setting:`DIRS <TEMPLATES-DIRS>` project-level directory first. In other words, :setting:`DIRS <TEMPLATES-DIRS>`
is searched before :setting:`APP_DIRS <TEMPLATES-APP_DIRS>`. is searched before :setting:`APP_DIRS <TEMPLATES-APP_DIRS>`.
.. seealso::
Read :ref:`overriding-built-in-widget-templates` if you're looking to
do that.
Overriding from the project's templates directory Overriding from the project's templates directory
================================================= =================================================

8
docs/ref/forms/renderers.txt
View File

@ -114,6 +114,8 @@ Some widgets add further information to the context. For instance, all widgets
that subclass ``Input`` defines ``widget['type']`` and :class:`.MultiWidget` that subclass ``Input`` defines ``widget['type']`` and :class:`.MultiWidget`
defines ``widget['subwidgets']`` for looping purposes. defines ``widget['subwidgets']`` for looping purposes.
.. _overriding-built-in-widget-templates:
Overriding built-in widget templates Overriding built-in widget templates
==================================== ====================================
@ -123,6 +125,6 @@ Each widget has a ``template_name`` attribute with a value such as
``input.html`` by defining ``django/forms/widgets/input.html``, for example. ``input.html`` by defining ``django/forms/widgets/input.html``, for example.
See :ref:`built-in widgets` for the name of each widget's template. See :ref:`built-in widgets` for the name of each widget's template.
If you use the :class:`TemplatesSetting` renderer, overriding widget templates To override widget templates, you must use the :class:`TemplatesSetting`
works the same as overriding any other template in your project. You can't renderer. Then overriding widget templates works :doc:`the same as
override built-in widget templates using the other built-in renderers. </howto/overriding-templates>` overriding any other template in your project.