Using the same template name multiple times with Flask and Jinja2
I have a Flask project with the following structure:
├── config.py
├── errors
│ ├── __init__.py
│ ├── handlers.py
│ └── templates
│ ├── errors
│ │ ├── 403.html
│ │ ├── 404.html
│ │ └── 500.html
│ └── default_layout.html
├── home
│ ├── __init__.py
│ ├── routes.py
│ └── templates
│ ├── about
│ │ └── general.html
│ └── default_layout.html
├── static
│ └── style.css
└── templates
└── default_layout.html
My app contains two blueprints: errors and home.
Is there a way for template files in my blueprints to extend multiple template files with the same filename? I have the following which results in an exception:
1) app/errors/templates/errors/403.html:
{% extends 'default_layout.html' %}
{% block error_content %}
<div class="content-section">
<h1>404 error</h1>
<p>{{ error }}</p>
</div>
{% endblock error_content %}
2) app/errors/templates/default_layout.html:
{% extends 'default_layout.html' %}
{% block content %}
<div class="content-section">
<h1>NESTED BLOCK</h1>
{% block error_content %}{% endblock %}
</div>
{% endblock content %}
3) app/templates/default_layer.html:
{% block content %}{% endblock %}
I want the default_layout.html
referenced in 1) to refer to 2) and the default_layout.html
referenced in 2) to refer to 3).
python flask jinja2
add a comment |
I have a Flask project with the following structure:
├── config.py
├── errors
│ ├── __init__.py
│ ├── handlers.py
│ └── templates
│ ├── errors
│ │ ├── 403.html
│ │ ├── 404.html
│ │ └── 500.html
│ └── default_layout.html
├── home
│ ├── __init__.py
│ ├── routes.py
│ └── templates
│ ├── about
│ │ └── general.html
│ └── default_layout.html
├── static
│ └── style.css
└── templates
└── default_layout.html
My app contains two blueprints: errors and home.
Is there a way for template files in my blueprints to extend multiple template files with the same filename? I have the following which results in an exception:
1) app/errors/templates/errors/403.html:
{% extends 'default_layout.html' %}
{% block error_content %}
<div class="content-section">
<h1>404 error</h1>
<p>{{ error }}</p>
</div>
{% endblock error_content %}
2) app/errors/templates/default_layout.html:
{% extends 'default_layout.html' %}
{% block content %}
<div class="content-section">
<h1>NESTED BLOCK</h1>
{% block error_content %}{% endblock %}
</div>
{% endblock content %}
3) app/templates/default_layer.html:
{% block content %}{% endblock %}
I want the default_layout.html
referenced in 1) to refer to 2) and the default_layout.html
referenced in 2) to refer to 3).
python flask jinja2
add a comment |
I have a Flask project with the following structure:
├── config.py
├── errors
│ ├── __init__.py
│ ├── handlers.py
│ └── templates
│ ├── errors
│ │ ├── 403.html
│ │ ├── 404.html
│ │ └── 500.html
│ └── default_layout.html
├── home
│ ├── __init__.py
│ ├── routes.py
│ └── templates
│ ├── about
│ │ └── general.html
│ └── default_layout.html
├── static
│ └── style.css
└── templates
└── default_layout.html
My app contains two blueprints: errors and home.
Is there a way for template files in my blueprints to extend multiple template files with the same filename? I have the following which results in an exception:
1) app/errors/templates/errors/403.html:
{% extends 'default_layout.html' %}
{% block error_content %}
<div class="content-section">
<h1>404 error</h1>
<p>{{ error }}</p>
</div>
{% endblock error_content %}
2) app/errors/templates/default_layout.html:
{% extends 'default_layout.html' %}
{% block content %}
<div class="content-section">
<h1>NESTED BLOCK</h1>
{% block error_content %}{% endblock %}
</div>
{% endblock content %}
3) app/templates/default_layer.html:
{% block content %}{% endblock %}
I want the default_layout.html
referenced in 1) to refer to 2) and the default_layout.html
referenced in 2) to refer to 3).
python flask jinja2
I have a Flask project with the following structure:
├── config.py
├── errors
│ ├── __init__.py
│ ├── handlers.py
│ └── templates
│ ├── errors
│ │ ├── 403.html
│ │ ├── 404.html
│ │ └── 500.html
│ └── default_layout.html
├── home
│ ├── __init__.py
│ ├── routes.py
│ └── templates
│ ├── about
│ │ └── general.html
│ └── default_layout.html
├── static
│ └── style.css
└── templates
└── default_layout.html
My app contains two blueprints: errors and home.
Is there a way for template files in my blueprints to extend multiple template files with the same filename? I have the following which results in an exception:
1) app/errors/templates/errors/403.html:
{% extends 'default_layout.html' %}
{% block error_content %}
<div class="content-section">
<h1>404 error</h1>
<p>{{ error }}</p>
</div>
{% endblock error_content %}
2) app/errors/templates/default_layout.html:
{% extends 'default_layout.html' %}
{% block content %}
<div class="content-section">
<h1>NESTED BLOCK</h1>
{% block error_content %}{% endblock %}
</div>
{% endblock content %}
3) app/templates/default_layer.html:
{% block content %}{% endblock %}
I want the default_layout.html
referenced in 1) to refer to 2) and the default_layout.html
referenced in 2) to refer to 3).
python flask jinja2
python flask jinja2
edited Nov 17 '18 at 20:55
iCode101
asked Nov 17 '18 at 20:27
iCode101iCode101
8619
8619
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
One approach is to further nest templates using the name of the blueprint as a scope. E.g.,
errors/templates/default_layout.html
would become
errors/templates/errors/default_layout.html
And using it would become {% extends "errors/default_layout.html" %}
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53355260%2fusing-the-same-template-name-multiple-times-with-flask-and-jinja2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
One approach is to further nest templates using the name of the blueprint as a scope. E.g.,
errors/templates/default_layout.html
would become
errors/templates/errors/default_layout.html
And using it would become {% extends "errors/default_layout.html" %}
add a comment |
One approach is to further nest templates using the name of the blueprint as a scope. E.g.,
errors/templates/default_layout.html
would become
errors/templates/errors/default_layout.html
And using it would become {% extends "errors/default_layout.html" %}
add a comment |
One approach is to further nest templates using the name of the blueprint as a scope. E.g.,
errors/templates/default_layout.html
would become
errors/templates/errors/default_layout.html
And using it would become {% extends "errors/default_layout.html" %}
One approach is to further nest templates using the name of the blueprint as a scope. E.g.,
errors/templates/default_layout.html
would become
errors/templates/errors/default_layout.html
And using it would become {% extends "errors/default_layout.html" %}
answered Nov 18 '18 at 1:47
Dave W. SmithDave W. Smith
16.3k22430
16.3k22430
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53355260%2fusing-the-same-template-name-multiple-times-with-flask-and-jinja2%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown