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 :-)
* Hyphenate classname: result_list => result-list
* Fixed gulp config for compiling scss
Was compiling to modeladmin/index.css instead of wagtailmodeladmin.css which caused the styles to not load
* Nest scss rules
Makes the scss easier to read I think
* Let choose_parent_page.scss use an id selector
* Converted ids to classes
* scss style tweaks
* Allow choose_parent_page.scss to use id selector
We should definitely solve this. But need to get Drone working right now
The test output was extremely noisy with deprecation warnings. Half of
these warnings were caused by external modules like django-taggit, and
could be ignored. The warnings caused by Wagtail got lost in the noise
though, rendering the test output useless for finding warnings. By
default, the tests now only print deprecation warnings if raised by
Wagtail.
Use `./runtests.py --deprecation=all` if you want all the warnings to be
printed. This is useful when we want to fix third party packages before
they break from being too outdated.
Use `./runtests.py --deprecation=pending` if you want the default
behaviour.
Use `./runtests.py --deprecation=imminent` if you only want imminent
DeprecationWarnings, ignoring PendingDeprecationWarnings.
Use `./runtests.py --deprecation=none` if you want to ignore all
deprecation warnings.
