Upgraded from 3.1 to 3.1.1 & I'm getting an AttributeError from the toolbar

[marksweb]

I've just upgraded a project to 3.1.1, cleaned pyc files, migrated & tried to load a page. This has resulted in an AttributeError;

File "/Users/mwalker/Sites/proj/lib/python2.7/site-packages/django/template/debug.py", line 90, in render
output = self.filter_expression.resolve(context)
File "/Users/mwalker/Sites/proj/lib/python2.7/site-packages/django/template/base.py", line 596, in resolve
obj = self.var.resolve(context)
File "/Users/mwalker/Sites/proj/lib/python2.7/site-packages/django/template/base.py", line 734, in resolve
value = self._resolve_lookup(context)
File "/Users/mwalker/Sites/proj/lib/python2.7/site-packages/django/template/base.py", line 788, in _resolve_lookup
current = current()
File "/Users/mwalker/Sites/proj/lib/python2.7/site-packages/cms/toolbar/toolbar.py", line 231, in get_object_public_url
with force_language(self.request.LANGUAGE_CODE):

AttributeError: 'WSGIRequest' object has no attribute 'LANGUAGE_CODE'

[aa-dit-yuh]

I faced the same problem.
Please ensure that you have 'django.middleware.locale.LocaleMiddleware' included in `MIDDLEWARE_CLASSES``.

[marksweb]

Nice, thanks @narayanaditya95 totally missed the fact that was missing!

[oliwarner]

Why is django.middleware.locale.LocaleMiddleware a requirement now? Kick it out, the code should fall back to settings.LANGUAGE_CODE (or self.language in that code, or something in between).

Please reopen and fix this.

[yakky]

django CMS needs the language in the request for a lot of things and thus needs LocaleMiddleware; this requirement won't go away

[oliwarner]

It didn't though. Barely a minor version ago cms/toolbar/toolbar.py was fine falling back on the settings as the default language. What has happened recently that makes this behaviour impossible or impractical?