Django-floppyforms

Latest version: v1.9.0

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

Scan your dependencies

Page 1 of 3

1.9.0

~~~~~

This release changes the compatibility matrix for the project.

We now support the following Django releases:
- Django 2.2
- Django 3.0

We are also testing under the following Python versions:
- Python 3.6
- Python 3.7
- Python 3.8


No other significant changes in this release, but Django 1.11 and 2.1
are no longer supported.

1.8.0

~~~~~

This is the first release to be done under the Jazzband organization.

It collects several compatibility fixes to support Django 1.11 and 2.1.

The currently tested versions of `django-floppyforms` is now:
- Django 1.11 and Python 2.7 or 3.6
- Django 2.1 and Python 3.6

In principle, we want to support any reasonable combination of Django and Python that still receives security releases, so if you are using an untested combination and hit an issue, bug reports are welcome.

*Breaking Change*:

Because Django's widgets now render through a form-specific template renderer, but `floppyforms` widgets
use the standard rendering template (that doesn't automatically include Django's form templates), it is
recommended to manuallyput Django's form template directory directly into your own template backend
configuration.

If you don't add the following, you might experience issues mixing and matching vanilla widgets with
floppyform widgets::

import django

TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [
..., your other template directories
django's own form template directories
os.path.join(os.path.dirname(django.__file__), "forms/templates/",
],
...
},
...
]


* `176`_: Fix HTML validation for hidden textarea used with GIS widgets.
* `191`_ + `196`_ + `209`_: Support for Django 1.11 and 2.1. Thanks to MrJmad and dryice for patches.
* `194`_: Remove official support for Python 2.6 and Python 3.2.
* `204`_: Use HTTPS for OpenStreetMap links. Thanks to dryice for the patch.

.. _176: https://github.com/jazzband/django-floppyforms/issues/176
.. _191: https://github.com/jazzband/django-floppyforms/pull/191
.. _194: https://github.com/jazzband/django-floppyforms/pull/194
.. _204: https://github.com/jazzband/django-floppyforms/pull/204
.. _196: https://github.com/jazzband/django-floppyforms/pull/196
.. _209: https://github.com/jazzband/django-floppyforms/pull/209

1.7.0

~~~~~

* `171`_: Fix path to GIS widget images in ``openlayers.html`` template. The
files coming with Django admin where used, but the naming changed in 1.9. We
vendor these know to have better control over it.
* `174`_: Support for setting your own Google Maps key in the
``BaseGMapWidget``. `See the documentation
<http://django-floppyforms.readthedocs.io/en/latest/geodjango.html>`_ for
details

.. _171: https://github.com/jazzband/django-floppyforms/issues/171
.. _174: https://github.com/jazzband/django-floppyforms/pull/174

1.6.2

~~~~~

* `169`_: Use the attributes ``ClearableFileInput.initial_text``,
``ClearableFileInput.input_text``,
``ClearableFileInput.clear_checkbox_label`` to determine the used text in the
template. This was inconsistent so far with Django's behaviour.

.. _169: https://github.com/jazzband/django-floppyforms/issues/169

1.6.1

~~~~~

* `167`_: Fix django-floppyforms' ``CheckboxInput.value_from_datadict`` which
was inconsistent with Django's behaviour.

.. _167: https://github.com/jazzband/django-floppyforms/issues/167

1.6.0

~~~~~

* `160`_: Django 1.9 support! Thanks to Jonas Haag for the patch.

.. _160: https://github.com/jazzband/django-floppyforms/pull/160

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.