TemplateNotFound if relative path passed to {% include %} in variable

[Peter Inglesby]

If you pass a template path as string literal to {% include %}, the template path can begin with eg ./, which is then resolved.

However, if you pass a template path in a variable to {% include %}, the ./ is not resolved and Django raises TemplateNotFound.

For instance, I have a template for rendering Bootstrap tab panels:

<div
      class="tab-pane fade p-4"
      id="{{ tab_name }}"
      role="tabpanel"
      aria-labelledby="{{ tab_name }}-tab"
>
  {% include template_path %}
</div>

This works:

{% include "./_bootstrap_panel.html" with tab_name="search-results" template_name="myapp/_search_results.html" %}

This doesn't:

{% include "./_bootstrap_panel.html" with tab_name="search-results" template_name="./_search_results.html" %}

[Mariusz Felisiak]

Thanks for this report, it works for {% extends %} but raises TemplateDoesNotExist for {% include %} (see attached tests).

[Hasan Ramezani]

​PR

[Mariusz Felisiak <felisiak.mariusz@…>]

In 640a6e1d:

Refs #32290 -- Added {% extends %} test for relative path in variable.

[Mariusz Felisiak <felisiak.mariusz@…>]

In c978dd93:

Fixed #32290 -- Fixed TemplateNotFound in {% include %} tag for relative path in variable.

[Mariusz Felisiak <felisiak.mariusz@…>]

In 73e7bfc:

[3.2.x] Fixed #32290 -- Fixed TemplateNotFound in {% include %} tag for relative path in variable.

Backport of c978dd93fda87c6d2e965d385164c35f1a3e64b8 from master

[Mariusz Felisiak <felisiak.mariusz@…>]

In 7d02fa94:

Refs #32290 -- Optimized construct_relative_path() by delay computing has_quotes.