wagtail/docs/releases/2.11.1.rst

============================
Wagtail 2.11.1 release notes
============================

.. contents::
    :local:
    :depth: 1


What's new
==========

Bug fixes
~~~~~~~~~

 * Ensure that cached ``wagtail_site_root_paths`` structures from older Wagtail versions are invalidated (Sævar Öfjörð Magnússon)
 * Avoid circular import between wagtail.admin.auth and custom user models (Matt Westcott)
 * Prevent error on resolving page URLs when a locale outside of ``WAGTAIL_CONTENT_LANGUAGES`` is active (Matt Westcott)
Fill in release date for 2.11.1 2020-11-06 18:29:59 +01:00			`============================`
			`Wagtail 2.11.1 release notes`
			`============================`
Add release notes section for 2.11.1 Conflicts: CHANGELOG.txt docs/releases/index.rst 2020-11-04 11:27:07 +01:00
			`.. contents::`
			`:local:`
			`:depth: 1`


			`What's new`
			`==========`

			`Bug fixes`
			`~~~~~~~~~`

Additional safeguard to check if a cached site is from an older version of Wagtail (#6515) 2020-11-04 00:42:39 +01:00			* Ensure that cached ``wagtail_site_root_paths`` structures from older Wagtail versions are invalidated (Sævar Öfjörð Magnússon)
Avoid circular import between wagtail.admin.auth and custom user models (#6522) Fixes #6518 If the models.py containing a custom user model directly or indirectly imports wagtail.admin.auth, this causes a circular dependency because wagtail.admin.auth attempts to import django.contrib.auth.views, which in turn depends on the custom user model. Fix this by moving the django.contrib.auth.views import inside reject_request. 2020-11-05 19:07:29 +01:00			`* Avoid circular import between wagtail.admin.auth and custom user models (Matt Westcott)`
Prevent errors on get_url_parts when a non-content-language locale is active (#6521) Fixes #6510 and #6511 Catch the LookupError from get_supported_content_language_variant so that if the active language is not one that is recognised as a content language, the URL prefix will be left unchanged from the page's reported locale. Additionally, skip the `translation.override` when WAGTAIL_I18N_ENABLED is false; this accounts for the fact that existing sites may have used alternative / custom i18n implementations involving i18n_patterns, and on these sites we can't rely on the page's locale field to be meaningful. That way, we restore the pre-2.11 behaviour: if the existing i18n code was using some kind of wrapper around the get_url_parts call, then that will work again; and if not, the URL will reflect the current active locale, which is no worse than before. 2020-11-05 17:44:36 +01:00			* Prevent error on resolving page URLs when a locale outside of ``WAGTAIL_CONTENT_LANGUAGES`` is active (Matt Westcott)