Emphasized that TemplatesSetting must be used to override widget templates.
This commit is contained in:
parent
32fbccab40
commit
25f4302349
|
@ -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>`
|
||||
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
|
||||
=================================================
|
||||
|
||||
|
|
|
@ -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`
|
||||
defines ``widget['subwidgets']`` for looping purposes.
|
||||
|
||||
.. _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.
|
||||
See :ref:`built-in widgets` for the name of each widget's template.
|
||||
|
||||
If you use the :class:`TemplatesSetting` renderer, overriding widget templates
|
||||
works the same as overriding any other template in your project. You can't
|
||||
override built-in widget templates using the other built-in renderers.
|
||||
To override widget templates, you must use the :class:`TemplatesSetting`
|
||||
renderer. Then overriding widget templates works :doc:`the same as
|
||||
</howto/overriding-templates>` overriding any other template in your project.
|
||||
|
|
Loading…
Reference in New Issue