I have the following template:
{% extends "account/base.html" %}
{% load i18n %}
{% load account %}
{% load crispy_forms_tags %}
{% block head_title %}{% trans "Password Reset" %}{% endblock %}
{% block content %}
<div class="container">
<div class="row justify-content-center">
<div class="col-8">
<h1>Reset your password</h1>
{% if user.is_authenticated %}
{% include "account/snippets/already_logged_in.html" %}
{% endif %}
<p>{% trans "Forgotten your password? Enter your e-mail address below, and we'll send you an e-mail allowing you to reset it." %}</p>
<form method="POST" action="{% url 'account_reset_password' %}" class="password_reset">
{% csrf_token %}
{{ form|crispy }}
<button type="submit" class="btn btn-primary">Reset My Password</button>
</form>
<p><em>{% blocktrans %}Please contact us if you have any trouble resetting your password.{% endblocktrans %}</em></p>
</div>
</div>
</div>
{% endblock %}
account/base.html contains this here:
{% extends "base.html" %}
base.html then contains tags etc. I am currently struggling with finding the best solution while considering DRY. In my template I have written:
<div class="container">
<div class="row justify-content-center">
<div class="col-8">
[more text]
</div>
</div>
</div>
I have several of these templates and in each of them I am currently writing the same ... I am now wondering is the right solution to include these opening / closing div-tags in two files and then add
{% include "div-open.html" %}
[more text]
{% include "div-closing.html" %}
Or is there any better solution to this? It doesn't feel right, that's why I am asking you now how you would solve this.
I depends if HTML repetition should be considered as DRY violation. I you have custom form fields which you want to include, than having {% include 'simple_custom_field.html' with field=form.some_fied %} where
simple_custom_field.html
<input
type="{{ field.field.widget.input_type }}"
class="form-control {{ field.field.widget.attrs.class }} {{ class }}"
id="{{ field.id_for_label }}"
name="{{ field.html_name }}"
placeholder="{{ field.label }}"
{% if field.value is not None %} value="{{ field.value }}"{% endif %}>
or like that...
is good idea, or you can render whole form like that also if you have long blocks or separate blocks of HTML in multiple files, then go for it. But its bad idea for including simple and fundamental parts of HTML. It should be transparent for the programmer.
If you want to do it another way, there are ways how to add custom template tags and "modify" the language you write templates in.
Here is docs how to do it: Writing custom template tags | Django docs
In Django's documentation there's an example that shows how a user can choose the language of the page. They fill and then submit a form.
This example works for me. However, I'd like to use a Bootstrap dropdown with a list of links to cause this behaviour. I have the idea to set the value of the "next" input to the code of the chosen language and submit the form. Here's the code:
<form name="ui" action="{% url 'set_language' %}" method="post">{% csrf_token %}
<input name="next" type="hidden" value="{{ redirect_to }}" />
<a class="dropdown-toggle" data-toggle="dropdown" href="#" role="button" aria-haspopup="true" aria-expanded="false">
{% get_current_language as LANGUAGE_CODE %}
{% get_language_info for LANGUAGE_CODE as lang %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{{ lang.name_local }}
<span class="caret"></span>
</a>
<ul class="dropdown-menu">
{% for language in languages %}
<li>{{ language.name_local }}</li>
{% endfor %}
</ul>
</form>
It generates the following html code (I left out csrf token, but it's there):
<form name="ui" action="/i18n/setlang/" method="post">
<input name="next" type="hidden" value="" />
<a class="dropdown-toggle" data-toggle="dropdown" href="#" role="button" aria-haspopup="true" aria-expanded="false">English<span class="caret"></span></a>
<ul class="dropdown-menu">
<li>English</li>
<li>German
</li>
</ul>
</form>
This leads (choosing German with "de" language code), however, to 404 error with Request URL http://127.0.0.1:8000/i18n/setlang/de (and, don't no why, with Request Method "GET").
What went wrong and how can I solve the problem?
p.s. The line
url(r'^i18n/', include('django.conf.urls.i18n')),
is there in urls.py
This is what works for me: adding an additional input element with the name "language"
Further, assign a language code for it in JS before submitting the form, i.e. document..language.value =
Then the part of template looks like this:
<form name="ui" action="{% url 'set_language' %}" method="post">{% csrf_token %}
<input name="next" type="hidden" value="{{ redirect_to }}" />
<input name="language" type="hidden"/>
<a class="dropdown-toggle" data-toggle="dropdown" href="#" role="button" aria-haspopup="true" aria-expanded="false">
{% get_current_language as LANGUAGE_CODE %}
{% get_language_info for LANGUAGE_CODE as lang %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{{ lang.name_local }}
<span class="caret"></span>
</a>
<ul class="dropdown-menu">
{% for language in languages %}
<li>{{ language.name_local }}</li>
{% endfor %}
</ul>
you can try this easier one:
{% load i18n %}
{% get_available_languages as languages %}
{% for language in languages %}
<li class="{% ifequal current_language language.0 %}active{% endifequal %}">
<a href="/./{{ language.0 }}/" title="{{ language.1 }}">
{{ language.1 }}
</a>
</li>
{% endfor %}
#doniyor an slightly modified version of your answer (consider using i18n context_processor )
{% with "/"|add:LANGUAGE_CODE as redundant %}
{% for language_code, _ in LANGUAGES %}
{% if language_code != LANGUAGE_CODE %}
<li>
<a class="text-decoration-none dropdown-item archive-link"
href="/{{ language_code }}{{ request.get_full_path|cut:redundant }}">
{{ language_code|language_name_local }} ({{ language_code }})
</a>
</li>
{% endif %}
{% endfor %}
{% endwith %}
I have a django 1.6 site with i18n working. I can change the frontend language with a select box in the top of the template, but I don't know if there is a django app or trick to change the admin language, because it seems to store somewhere in session variable, and it keeps the first language I have used in the frontend.
In your settings.py just add 'django.middleware.locale.LocaleMiddleware' to your MIDDLEWARE_CLASSES setting, making sure it appears after 'django.contrib.sessions.middleware.SessionMiddleware'.
You can create /en/admin, /fr/admin/ and so on using i18n_patterns:
urlpatterns += i18n_patterns(
url(r'^admin/', include(admin.site.urls)),
)
(For Django <= 1.7, you must specify a prefix, use i18n_patterns('', ... ))
Here is a slightly modified version of a code snippet from the Django docs for admin/base.html that adds a language selection dropdown:
{% extends "admin/base.html" %}
{% load i18n %}
{% block userlinks %}
{{ block.super }}
/ <form action="{% url 'set_language' %}" method="post" style="display:inline">{% csrf_token %}
<input name="next" type="hidden" value="{{ redirect_to }}">
<select name="language" onchange="this.form.submit()">
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<option value="{{ language.code }}"{% if language.code == LANGUAGE_CODE %} selected{% endif %}>
{{ language.name_local }} ({{ language.code }})
</option>
{% endfor %}
</select>
</form>
{% endblock %}
For this to work you also need to add the following to your urlpatterns:
path('i18n/', include('django.conf.urls.i18n')),
I need to include two buttons or links to allow users change language between English and Spanish. I've read the docs and tried this:
<form action="/i18n/setlang/" method="post">{% csrf_token %}
<input name="language" type="hidden" value="es" />
<input type="submit" value="ES" />
</form>
However, every time I click the button, the page is reloaded but the language doesn't change at all. Am I missing something?
Note: I haven't set next, as I just want to reload the current page in the desired language.
If I use the default form provided by the docs the result is the same: the page reloads but language isn't changed:
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<input name="next" type="hidden" value="{{ redirect_to }}" />
<select name="language">
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<option value="{{ language.code }}"{% if language.code == LANGUAGE_CODE %} selected="selected"{% endif %}>
{{ language.name_local }} ({{ language.code }})
</option>
{% endfor %}
</select>
<input type="submit" value="Go" />
</form>
UPDATE:
After further testing, I've noticed that there is a problem using both i18n_patterns and patterns in the urls.py. Currently I have a file that looks like:
urlpatterns = i18n_patterns('',
url(r'^contents/', include('contents.urls')),
url(r'^events/', include('events.urls')),
# ...
)
urlpatterns += patterns('',
url(r'^i18n/', include('django.conf.urls.i18n')),
)
And this doesn't seem to work. However, if I remove the i18n_patterns and change it to patterns then it seems to work:
urlpatterns = patterns('',
url(r'^contents/', include('contents.urls')),
url(r'^events/', include('events.urls')),
# ...
)
urlpatterns += patterns('',
url(r'^i18n/', include('django.conf.urls.i18n')),
)
The docs say that you don't have to include it inside i18n_patterns, so I think this should work, but it doesn't! It doesn't matter if you include django.conf.urls.i18n before or after i18n_patterns it always does the same.
After more testing and thanks to the related question linked by #AronYsidoro I've finally found the issue and a very simple solution that actually solves this.
First, let me explain the problem: When working with i18_patterns in your urls.py to prepend the language code, if you call the URL set_language to change the language without specifying next, it defaults to the current one, but with the prepended old language code! So, the language gets back to the original! And, if you explicitly specify next, you must be sure to do not include the language code at the begining.
If you use {{ request.path }} or {{ request.get_full_path }} to specify the next as the current page this won't work as it returns the language code too.
So, how do we remove this undesired language code to reload the current page with the language changed when using i18n_patterns? Easy, we just have to slice the 3 first chars (the slash and the two chars language code)!
Here you have two examples. The first one in form of a select (with the languages as choices) and the other one in form of a button (per language).
I really hope this helps someone else. You can just copy and paste the code and it should work. However, if using the "button form", you just have to set the language to your desired!
Change language from list:
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<input name="next" type="hidden" value="{{ request.get_full_path|slice:'3:' }}" />
<select name="language">
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<option value="{{ language.code }}"{% if language.code == LANGUAGE_CODE %} selected="selected"{% endif %}>
{{ language.name_local }} ({{ language.code }})
</option>
{% endfor %}
</select>
<input type="submit" value="Change" />
</form>
Change language as button:
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<input name="next" type="hidden" value="{{ request.get_full_path|slice:'3:' }}" />
<input name="language" type="hidden" value="es" />
<input type="submit" value="ES" />
</form>
A sum-up of possible options:
Change the user's session language with a select
There is an excellent extensive description with example on Django docs.
Change the user's session language with buttons
There is no need to repeat a form for each button as #Caumons suggested, instead you can simply include as many buttons in the form as the languages.
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<input name="next" type="hidden" value="{{ request.get_full_path|slice:'3:' }}" />
<ul class="nav navbar-nav navbar-right language menu">
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<li>
<button type="submit"
name="language"
value="{{ language.code }}"
class="{% if language.code == LANGUAGE_CODE %}selected{% endif %}">
{{ language.name_local }}
</button>
</li>
{% endfor %}
</ul>
</form>
You can certainly style up the buttons to look like links or whatever.
Change the language displayed with links
If it is not required that the default user session language is changed, then simple links can be used to change the content:
<ul class="nav navbar-nav navbar-right language menu">
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<li>
<a href="/{{ language.code }}{{ request.get_full_path|slice:'3:' }}"
class="{% if language.code == LANGUAGE_CODE %}selected{% endif %}"
lang="{{ language.code }}">
{{ language.name_local }}
</a>
</li>
{% endfor %}
</ul>
SEO
I am not entirely sure that the content is seo friendly if a form is used to change the session language, as Django recommends. Therefore it is possible that the link <a> markup is added as hidden below the <button> element.
If in your current system you have only 2 languages then simply use like below:
{% ifequal LANGUAGE_CODE "en" %}
Spanish
{% else %}
English
{% endifequal %}
No need of a form, url and submit etc. It worked for me.
Besides adding form that was suggested here:
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
{{ request.get_full_path_info|slice:'3:'}}
<input name="next" type="hidden" value="{{ languageless_url }}" />
<ul class="nav navbar-nav navbar-right language menu">
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<li>
<button type="submit" name="language" value="{{ language.code }}"
class="{% if language.code == LANGUAGE_CODE %}selected{% endif %}">
{{ language.code }}
</button>
</li>
{% endfor %}
</ul>
</form>
I would suggest adding a context processor (app.context_processors.py):
def language_processor(request):
"""
This is needed for language picker to work
"""
return {
'languageless_url':
'/' + '/'.join(request.get_full_path().split('/')[2:])
}
This allows to leave the logic out of template.
Also don't forget to add your processor in template settings:
'context_processors': [
'app.context_processors.language_processor',
If you only need two languages, ex. English and French and you've defined this in your settings.py and you have set the default language and you have configured urls.py in your main app correctly. Then, just use this in your template (or partial, topbar etc.) btn-kinito "btn-header are just styling classes you can manipulate that with css or JS.
The loop or iteration inside is just looping through the LANGUAGES[] list, which you've defined in settings.py, then it creates a button. with the character "|" and a space to make it look cute since we have just two langs.
The {% url 'set_language' %} is Django's redirect view called set_language it redirects to URL. This is why in your main apps's urls.py you need to put path('i18n/', include('django.conf.urls.i18n')), In this case. So after the button is created for each language in the list you will be able to be redirected to that url.
<div class="btn-header">
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<input name="next" type="hidden" value="{{ redirect_to }}" />
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<button type="submit" name="language" value="{{ language.code }}"
class="btn-kinito">
{{ language.code }}
</button>|
{% endfor %}
</form>
</div>
For urls.py I think it could look like this:
from django.contrib import admin
from django.urls import path, include
from django.conf import settings
from django.conf.urls.static import static
from django.conf.urls.i18n import i18n_patterns
# I don't want my admin translated
urlpatterns = [
path('admin/', admin.site.urls),
]
urlpatterns += i18n_patterns (
path('i18n/', include('django.conf.urls.i18n')),
path('', include('pages.urls')),
path('cats', include('cats.urls')),
path('dogs', include('dogs.urls')),
prefix_default_language=False,
) + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)
The prefix_default_language=False, this is optional and it removes the default language prefix from the url, which makes sense if you just got two or three languages. Although I did run into problems with this in the past, where the prefix_default_language=False, did not work.
How to fix the problem with prefix_default_language=False, NOT working, or not removing the default language prefix from urls
In my settings.py I changed:
LANGUAGE_CODE = 'en-us' to LANGUAGE_CODE = 'en'
(seems to have solved it)
I know it's not a solid solution but I needed a switch button (not a dropdown list since I want to toggle between two languages)
So I came up with this:
{% get_language_info_list for LANGUAGES as languages %}
{% if LANGUAGE_CODE == languages.0.code %}
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<div class="lang-btn">
<input name="next" type="hidden" value="{{ redirect_to }}" />
<input name="language" type="hidden" value="{{ languages.1.code }}" />
<button type="submit"><img width="30" src="{% static 'united-kingdom.png' %}" alt=""></button>
</div>
</form>
{% else %}
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<div class="lang-btn">
<input name="next" type="hidden" value="{{ redirect_to }}" />
<input name="language" type="hidden" value="{{ languages.0.code }}" />
<button type="submit"><img width="30" src="{% static 'turkey.png' %}" alt=""></button>
</div>
</form>
{% endif %}
{% load i18n %}
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
<div class="btn-header">
<form action="{% url 'set_language' %}" method="post">
{% csrf_token %}
<input name="next" type="hidden" value="{{ redirect_to }}" />
{% for language in languages %}
{% if language.code != LANGUAGE_CODE %}
<button type="submit" name="language" value="{{ language.code }}">{{ language.name }}</button>
{% endif %}
{% endfor %}
</form>
</div>
if you have two languages. It will only show you the one that's off.
https://www.loom.com/share/9319c0e9204f417a8eec897965ce3a96
Django 3.02
<div class="uk-flex">
{% get_current_language as LANGUAGE_CODE %}
{% get_available_languages as LANGUAGES %}
{% get_language_info_list for LANGUAGES as languages %}
<div class="languages">
<p>{% trans "Language" %}:</p>
<ul class="languages">
{% for language in languages %}
<li>
<a href="/{{ language.code }}/{{ request.get_full_path |slice:'4:'}}" {% if language.code == LANGUAGE_CODE %} class="selected"{% endif %}>
{{ language.name_local }}
</a>
</li>
{% endfor %}
</ul>
</div>
</div>
Seems lot of people have spend a lot of time (like myself) finding a proper solution that works for all cases. "Trick" is to set next = '' if you want to reload existing page in different language. Citing from the django doc:
After setting the language choice, Django looks for a next parameter in the POST or GET data. If that is found and Django considers it to be a safe URL (i.e. it doesn’t point to a different host and uses a safe scheme), a redirect to that URL will be performed. Otherwise, Django may fall back to redirecting the user to the URL from the Referer header
Finally I wanted to have a function that I can call for any language changes triggered by links, buttons, dropdown menus or whatever. I ended up with this little js function:
django_language_set(language_code){
url = "{% url 'set_language' %}";
data = {
language: language_code,
next: '',
csrfmiddlewaretoken: '{{ csrf_token }}'
};
this.form_post(url, data)
}
form_post(path, params, method='post') {
/* simulates a post submit, call like:
form_post('/home', {language: 'de', next: ''})"
*/
const form = document.createElement('form');
form.method = method;
form.action = path;
for (const key in params) {
if (params.hasOwnProperty(key)) {
const hiddenField = document.createElement('input');
hiddenField.type = 'hidden';
hiddenField.name = key;
hiddenField.value = params[key];
form.appendChild(hiddenField);
}
}
document.body.appendChild(form);
form.submit();
}
Call the function, e.g.
<a #click="django_language_set('fr')">French</a>
I'm developing a multilingual blog and the example code in the django's documentation works for me
<form action="/i18n/setlang/" method="post">
{% csrf_token %}
<select name="language">
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
<option value="{{ language.code }}">{{ language.name_local }} ({{ language.code }})</option>
{% endfor %}
</select>
<input type="submit" value="Go" />
</form>
This form let the user choose the language they want. But I actually want to put it in the form of links like:
[FR][EN][VI]
How can I implement that in the templates?
Using jquery:
<form action="/i18n/setlang/" method="post" style="display: none" id="change_language_form">
{% csrf_token %}
<input type="hidden" value="" name="language" id="language" />
</form>
{% get_language_info_list for LANGUAGES as languages %}
{% for language in languages %}
{{ language.name_local }} ({{ language.code }})
{% endfor %}
<script>
$('.change_language').click(function(e){
e.preventDefault();
$('#language').val($(this).attr('lang_code'));
$('#change_language_form').submit();
});
</script>