From cf6c754629a6348847cf0e83a0ffbc8a74547641 Mon Sep 17 00:00:00 2001 From: Sergio Oliveira <sergio@tracy.com.br> Date: Thu, 18 Jul 2013 21:15:30 -0300 Subject: [PATCH] LocaleMiddleware isn't default anymore Changed in @23229061fcb836ecca2195cc75f91e331279a5d1 --- docs/topics/i18n/translation.txt | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt index 0d51bac504..e724837ce1 100644 --- a/docs/topics/i18n/translation.txt +++ b/docs/topics/i18n/translation.txt @@ -29,9 +29,7 @@ use internationalization, you should take the two seconds to set :setting:`USE_I18N = False <USE_I18N>` in your settings file. Then Django will make some optimizations so as not to load the internationalization machinery. You'll probably also want to remove ``'django.core.context_processors.i18n'`` -from your :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting and -``'django.middleware.locale.LocaleMiddleware'`` from your -:setting:`MIDDLEWARE_CLASSES` setting. +from your :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting. .. note:: @@ -1563,15 +1561,9 @@ If you want to let each individual user specify which language he or she prefers, use ``LocaleMiddleware``. ``LocaleMiddleware`` enables language selection based on data from the request. It customizes content for each user. -``LocaleMiddleware`` is enabled in the default settings file: the -:setting:`MIDDLEWARE_CLASSES` setting contains -``'django.middleware.locale.LocaleMiddleware'``. - -.. versionchanged:: 1.6 - - In previous versions, ``LocaleMiddleware`` wasn't enabled by default. - -Because middleware order matters, you should follow these guidelines: +To use ``LocaleMiddleware``, add ``'django.middleware.locale.LocaleMiddleware'`` +to your :setting:`MIDDLEWARE_CLASSES` setting. Because middleware order +matters, you should follow these guidelines: * Make sure it's one of the first middlewares installed. * It should come after ``SessionMiddleware``, because ``LocaleMiddleware``