We're updated the BlogEntryPage model to use class-based api_fields but
API v1 doesn't support them. This commit adds enough compatibility to
make the v1 API tests work but issues a warning if the v1 API module
encounters any new style configs that it doesn't support.
The only purpose it served was to tell you the date format - which is redundant since the date picker does that for you, and is no longer accurate when the format has been customised.
It is possible to set default format for date/datetime inputs. This works together
with standard django localization.
# django settings
USE_I18N = True
LANGUAGE_CODE = 'sl'
# wagtail settings
WAGTAIL_DATE_FORMAT = '%d.%m.%Y.'
WAGTAIL_DATETIME_FORMAT = '%d.%m.%Y. %H:%M'
DateBlock, DateTimeBlock accepts additional keyword argument `format`.
pk = quote(getattr(obj, self.opts.pk.attname))
self.url_helper.get_action_url('edit', quote(pk)) # < this was a little unneccessary, double function calls in multiple locations
This fixes the bug reported by @nimasmi in
https://github.com/wagtail/wagtail/issues/3431#issuecomment-288051751
Slicing creates a new SearchResults object but the ``score_field`` (set
by ``.annotate_score()`` wasn't being passed along to the new
SearchResults causing the score to not be annotated.
* Split `helpers.py` into separate `url.py`, `permission.py` and `button.py`, dedicated to those separate concerns and update the docs accordingly
* Move `ThumbnailMixin` out to `mixins.py` and update documentation accordingly
* Ad #NOQA to import lines to hush pep errors
* Alphabetise helper import order
* - Delete `helpers/helpers.py`
- wagtal -> wagtail in docs
* Add appyveyor config
This commit does add settings for using mssql on appveyor
but there are still some issues with timeouts. For now only
the sqlite build is enabled.
Note that the build currently (correctly) fails on windows
* Fix unittests on Windows (in wagtaildocs)
The document.file.name attribute doesn't contain a valid path separator
on windows. Use document.file.path for comparison instead.
