3👍
I don’t think this is possible. Just for your specific problem I guess it can be solves if you would place the site name before the block, and use the block just to append something to the site name.
Otherwise you could define SITE_NAME in your settings.py and have a context processor like
from django.conf import settings
def site_name(request):
return {'SITE_NAME': settings.SITE_NAME}
so that you can use {{ SITE_NAME }} in your templates – this could make sense because the site name could be usefule at other places too…
8👍
Note, Django 1.2.3 seems to already do what you want. Assuming SITE_NAME is exposed via a context_preprocessor like lzerscience illustrates, block.super should expose it through all the layers of inheritance.
main.html
{% extends "default.html" %}
{% block title %} {{ block.super }} - MAIN{% endblock %}
That displays the title “SITE NAME – SECTION NAME – MAIN” for me.
- You cannot add messages without installing django.contrib.messages.middleware.MessageMiddleware
- Django: Built-in include tag vs custom inclusion tag
- Creating one Django Form to save two models
- How to use custom token model in Django Rest Framework
- Django unit test client response has empty context
2👍
Django 1.6.6
{{ block.super.super }} – possible
I try now – worked 🙂
But not officially …
- What is the main difference between clean and full_clean function in Django?
- Django model subclassing approaches
- Django filter by datetime on a range of dates