Releases: wagtail/wagtail-autocomplete
Releases · wagtail/wagtail-autocomplete
Version 0.11.0
- Add handling of validation errors during creation of objects. This means when you write an
autocomplete_create
method on one of your Django models, you can raise aValidationError
during that method and wagtail-autocomplete will catch it and return a 400 response to the client, which gives the end-user a more informative error message. - Fix bug where searches failed if Django's CSRF cookie was configured with CSRF_COOKIE_HTTPONLY set to True
- Update Javascript dependencies to remove security vulnerabilities.
Version 0.10.0
- Change the search view to use the HTTP POST method, which can prevent the request URI from becoming too long.
- New feature: add the possibility of a custom filter function.
Version 0.9.0
- Add Wagtail 3.x compatibility
Version 0.8.1
- Change in behavior: the autocomplete endpoint will return a 404 response if no objects are found.
- Update Javascript dependencies to remove security vulnerabilities
Version 0.7.0
- Breaking change: Drop deprecated
page_type
andis_single
arguments fromAutocompletePanel
- Update the panel and widget codes based on panels of
wagtail.admin.edit_handlers
- mainlyPageChooserPanel
- Security updates of NPM dependencies
- Update use of deprecated
django.conf.urls.url
function.
Version 0.6.3
- Remove native browser autocomplete from field
Version 0.6
* Add Wagtail 2.8 support
v0.5: v.0.5: Version 0.5
* Add Django 3.0 support * Remove Wagtail 1.x support (Wagtail 2.3 or later now required) * Documentation fixes
v0.4: Version 0.4
* Deprecate is_single option, make target_model optional. AutocompletePanel will now automatically derive these attributes from the field. (#48) * Remove compatibility for all Python 2.x and Wagtail 1.x versions (#53)
v0.3.1
- Correct documentation for installing tests
- Correct errors raised by endpoints