[1.11.x] Fixed #28190 -- Clarifed how include/extends treat template names.
Backport of 1f2e4f9cfe
from master
This commit is contained in:
parent
34ea3d61af
commit
9a3bcaf46a
|
@ -215,8 +215,9 @@ This tag can be used in two ways:
|
|||
|
||||
See :ref:`template-inheritance` for more information.
|
||||
|
||||
A string argument may be a relative path starting with ``./`` or ``../``. For
|
||||
example, assume the following directory structure::
|
||||
Normally the template name is relative to the template loader's root directory.
|
||||
A string argument may also be a relative path starting with ``./`` or ``../``.
|
||||
For example, assume the following directory structure::
|
||||
|
||||
dir1/
|
||||
template.html
|
||||
|
@ -682,8 +683,9 @@ This example includes the contents of the template ``"foo/bar.html"``::
|
|||
|
||||
{% include "foo/bar.html" %}
|
||||
|
||||
A string argument may be a relative path starting with ``./`` or ``../`` as
|
||||
described in the :ttag:`extends` tag.
|
||||
Normally the template name is relative to the template loader's root directory.
|
||||
A string argument may also be a relative path starting with ``./`` or ``../``
|
||||
as described in the :ttag:`extends` tag.
|
||||
|
||||
.. versionadded:: 1.10
|
||||
|
||||
|
|
Loading…
Reference in New Issue