mirror of
https://github.com/wagtail/wagtail.git
synced 2024-11-28 17:13:31 +01:00
80ad8ffc94
If the developer had overridden MESSAGE_TAGS in their site, Wagtail messages used these classes in the admin. This caused the messages to lose their styles. Wagtail now ignores the MESSAGE_TAGS setting, using the default classes defined in `django.contrib.messages.constants.LEVEL_TAGS`. Fixes #2551
25 lines
1.2 KiB
ReStructuredText
25 lines
1.2 KiB
ReStructuredText
===========================
|
|
Wagtail 1.4.4 release notes
|
|
===========================
|
|
|
|
.. contents::
|
|
:local:
|
|
:depth: 1
|
|
|
|
|
|
What's changed
|
|
==============
|
|
|
|
Bug fixes
|
|
~~~~~~~~~
|
|
|
|
* The ``wagtailuserbar`` template tag now gracefully handles situations where the ``request`` object is not in the template context (Matt Westcott)
|
|
* Meta classes on StreamField blocks now handle multiple inheritance correctly (Tim Heap)
|
|
* Now user can upload images / documents only into permitted collection from choosers
|
|
* Keyboard shortcuts for save / preview on the page editor no longer incorrectly trigger the "unsaved changes" message (Jack Paine / Matt Westcott)
|
|
* Redirects no longer fail when both a site-specific and generic redirect exist for the same URL path (Nick Smith, João Luiz Lorencetti)
|
|
* Wagtail now checks that Group is registered with the Django admin before unregistering it (Jason Morrison)
|
|
* Previewing inaccessible pages no longer fails with ``ALLOWED_HOSTS = ['*']`` (Robert Rollins)
|
|
* The submit button 'spinner' no longer activates if the form has client-side validation errors (Jack Paine, Matt Westcott)
|
|
* Overriding ``MESSAGE_TAGS`` in project settings no longer causes messages in the Wagtail admin to lose their styling (Tim Heap)
|