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
Concatinating with settings.STATIC_URL is no longer reccomended for creating
URLs to static resources, because it doesn't take the configured storage engine
into account. For example, a site using S3 to store its static files will need
static URLs that link out to S3, rather than relative URLs within the same
domain.
I replaced it with django.contrib.staticfiles.templatetags.staticfiles.static()
in python example code, and the {% static %} tag in template examples.
Most of the samples were already 4-space indented, but a few were using 2-space,
which is both inconsistent and, when it happened with Python code samples,
incompatible with PEP8.
You get a lexer error from the document builder if you use "code-block:: json",
and the json-style highlighting ends up not being applied. So I switched it to
"code-block:: text".
Switching explorer from position absolute to position fixed.
I did it in a pure CSS way but it would be good to be able to modify jquery.dlmenu.js line 213 to avoid it adding automatically a CSS property top on the element.
Make collection field on document chooser upload respect user permissions
failing test for #2511 for image uploader
Make collection field on image chooser upload respect user permissions
Developer settings were always imported whenever any portion of the
project template settings package itself was imported. Using production
settings would result in __init__.py importing the dev settings first,
*then* overriding those with the production settings.
This lead to somewhat counter-intuitive behaviour - dev settings that
weren't explicitly set again in production would tag along to prod.
To fix this, the project template settings package no longer imports
dev, and settings.dev is explicitly used in both manage.py and wsgi.py.
Indexing the tags of TagSearchable subclasses (such as wagtailimages.Image) is done by following
the model's 'tags' relation, and wagtailsearch is smart enough to prefetch that automatically
(as the test demonstrates). Prefetching 'tagged_items__tag' just adds two useless queries :-)
