Wagtail-autocomplete

Latest version: v0.12.0

Safety actively analyzes 723158 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 2

0.6.3

Not secure
-------------

* Remove native browser autocomplete form field.

0.6

Not secure
-----------

* Add Wagtail 2.8 support

0.5

Not secure
-----------

* Add Django 3.0 support
* Remove Wagtail 1.x support (Wagtail 2.3 or later now required)
* Documentation fixes

0.4

Not secure
-----------

* Deprecate ``is_single`` option, make ``target_model`` optional. ``AutocompletePanel`` will now automatically derive these attributes from the field. (`48 <https://github.com/wagtail/wagtail-autocomplete/pull/48>`_)
* Remove compatibility for all Python 2.x and Wagtail 1.x versions (`53 <https://github.com/wagtail/wagtail-autocomplete/pull/53>`_)

0.3.1

Not secure
-------------

* Correct documentation for installing tests (`44 <https://github.com/wagtail/wagtail-autocomplete/pull/44>`_)
* Correct errors raised by endpoints (`45 <https://github.com/wagtail/wagtail-autocomplete/pull/45>`_)

0.3

Not secure
-----------

* Various improvements to Tox testing and CI setup.
* Various improvements to Webpack compilation.
* Replace ``page_type`` keyword argument with more accurate ``target_model`` keyword argument. The old argument still works, but is deprecated.
* Enable autocomplete panel to run its javascript function when it is added to the page dynamically. This allows autocomplete panels to function inside of inline panels.
* Change references from model IDs to model PKs to allow panel compatibility with custom and non-integer primary keys.

Page 2 of 2

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.