- #176: Fix HTML validation for hidden textarea used with GIS widgets.
- #171: Fix path to GIS widget images in
openlayers.htmltemplate. 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 for details
- #169: Use the attributes
ClearableFileInput.initial_text,ClearableFileInput.input_text,ClearableFileInput.clear_checkbox_labelto determine the used text in the template. This was inconsistent so far with Django's behaviour.
- #167: Fix django-floppyforms'
CheckboxInput.value_from_datadictwhich was inconsistent with Django's behaviour.
- #160: Django 1.9 support! Thanks to Jonas Haag for the patch.
- #156: The
min,max,stepattributes forDecimalFieldandFloatFieldwere localized which can result in invalid values (rendering0.01as0,01in respective locales). Those attributes won't get localized anymore. Thanks to Yannick Chabbert for the fix.
- FloatField` now fills in
min,max, andstepattributes to match the behaviour of DecimalField. Leaving out thestepattribute would result in widgets that only allow integers to be filled in (HTML 5 default forstepis1).
- #148: Added support for custom
label_suffixarguments in forms and fields. - The contents in
floppyforms/input.htmlis now wrapped in a{% block content %}for easier extending. - #70: DecimalField` now fills in
min,max, andstepattributes for better client side validation. Use thenovalidateattribute on your<form>tag to disable HTML5 input validation in the browser. Thanks to caacree for the patch.
- Fixed source distribution to include all files in
floppyforms/static/floppyforms/openlayers.
- Every widget is now using its own template. Previously all widgets that are
based on the HTML
<input>tag used the genericfloppyforms/input.htmltemplate. Now the widgets each have a custom element for easier customisation. For exampleCheckboxInputnow usesfloppyforms/checkbox.htmlinstead offloppyforms/input.html. See Widgets reference for a complete list of available widgets and which templates they use. - Adjusting the SRIDs used in the GeoDjango widgets to conform with Django 1.7. Thanks to Tyler Tipton for the patch.
- Python 3.2 is now officially supported.
- Django 1.8 is now officially supported. django-floppyforms no longers triggers Django deprecation warnings.
- Adding OpenLayers distribution to django-floppyforms static files in order to better support HTTPS setups when GIS widgets are used (See #15 for more details).
- Fix:
python setup.py bdist_rpmfailed because of wrong string encodings in setup.py. Thanks to Yuki Izumi for the fix. - Fix: The
CheckboxInputwidget did detect different values in Python 2 when given'False'andu'False'as data. Thanks to @artscoop for the patch. - Fix:
MultipleChoiceFieldcan now correctly be rendered as hidden field by using theas_hiddenhelper in the template. That was not working previously as there was no value set forMultipleChoiceField.hidden_widget.
- DateInput widget renders hardcoded "%Y-%m-%d" format. We don't allow custom formats there since the "%Y-%m-%d" format is what browsers are submitting with HTML5 date input fields. Thanks to Bojan Mihelac for the patch.
- Adding
supports_microsecondsattribute to all relevant widget classes. Thanks to Stephen Burrows for the patch. - Using a property for
Widget.is_hiddenattribute on widgets to be in conformance with Django 1.7 default widget implementation. - The docs mentioned that the current
ModelFormbehaviour infloppyforms.__future__will become the default in 1.3. This is postpone for one release and will be part of 1.4.
Subclasses of
floppyforms.models.ModelFormdid not convert widgets of form fields that were automatically created for the existing model fields into the floppyform variants. This is now changed, thanks to a patch by Stephen Burrows.Previously you had to set the widgets your self in a model form. For example you would write:
import floppyforms as forms class ProfileForm(forms.ModelForm): class Meta: model = Profile widgets = { 'name': forms.TextInput, 'url': forms.URLInput, ... }Now this is done automatically. But since this is a kind-of backwardsincompatible change, you need to use a special import:
import floppyforms.__future__ as forms class ProfileForm(forms.ModelForm): class Meta: model = ProfileThis feature will become the default behaviour in floppyforms 2.0.
See the documentation for more information: http://django-floppyforms.readthedocs.org/en/latest/usage.html#modelforms
If you added an attribute with value 1 to the attrs kwargs (e.g.
{'value': 1}, you would get no attribute value in the rendered html (e.g.valueinstead ofvalue="1"). That's fixed now, thanks to Viktor Ershov for the report.All floppyform widget classes now take a
template_nameargument in the__init__andrendermethod. Thanks to Carl Meyer for the patch.
- Fix for Django 1.6
- Fix for GIS widgets on Django 1.4 and some versions of GEOS.
- Added GenericIPAddressField.
- Django 1.5 and Python 3.3 support added.
- Django 1.3 support dropped.
- GIS widgets switched to stable OpenLayers release instead of a dev build.
- Fixed
Textareawidget template to work with a non-emptyTEMPLATE_STRING_IF_INVALIDsetting. Thanks to Leon Matthews for the report. - Fixed context handling in widget rendering. It didn't take care of popping the context as often as it was pushed onto. This could cause strange behaviour in the template by leaking variables into outer scopes. Thanks to David Danier for the report.
- Added missing empty choice for selectboxes in
SelectDateWidget. Thanks fsx999 for the report. IntegerFieldnow automatically passes itsmin_valueandmax_value(if provided) to theNumberInputwidget.- Added basic support for
<datalist>elements for suggestions inInputwidgets. date,datetimeandtimeinputs are not localized anymore. The HTML5 spec requires the rendered values to be RFC3339-compliant and the browsers are in charge of localization. If you still want localized date/time inputs, use those provided by Django or override the_format_value()method of the relevant widgets.
- cleaned up the behaviour of
attrs - compatible with Django 1.3 and 1.4
<optgroup>support in select widgetsSelectwidgets: renamedchoicescontext variable tooptgroups. This is backwards-incompatible: if you have custom templates forSelectwidgets, they need to be updated.get_context()is more reliable- Added
form,formrow,formfield,formconfigandwidgettemplate tags. - Added template-based form layout system.
- Added ability to render widgets with the broader page context, for instance for django-sekizai compatibility.
- All widgets from Django have their floppyforms equivalent
- Added widgets for GeoDjango