djangodocs.org

711 sections in Django dev Search all versions →

Forms

Release notes Django 1.8 release notes

Form widgets now render attributes with a value of True or False as HTML5 boolean attributes. The new has_error() method allows checking if a specific error has happened.

Bugfixes

Release notes Django 1.11.6 release notes

Made the CharField form field convert whitespace-only values to the empty_value when strip is enabled (#28555). Fixed crash when using the name of a model’s autogenerated primary key (id) in an Index’s fields (#28597).

Miscellaneous

Release notes Django 5.0 release notes

The DjangoDivFormRenderer and Jinja2DivFormRenderer transitional form renderers are deprecated. Passing positional arguments name and violation_error_message to BaseConstraint is deprecated in favor of keyword-only arguments. request is added to the signature of ModelAdmin.lookup_allowed().

Bugfixes

Release notes Django 1.10.6 release notes

Fixed ClearableFileInput’s “Clear” checkbox on model form fields where the model field has a default (#27805). Fixed RequestDataTooBig and TooManyFieldsSent exceptions crashing rather than generating a bad request response (#27820).

Forms

Release notes Django 5.2 release notes

The new ColorInput form widget is for entering a color in rrggbb hexadecimal format and renders as <input type="color" ...>. Some browsers support a visual color picker interface for this input type.

Release notes Django 1.11 release notes

To ease customizing widgets, form widget rendering is now done using the template system rather than in Python. See The form rendering API. You may need to adjust any custom widgets that you’ve written for a few backwards incompatible changes.

Release notes Django 1.3 release notes

The PasswordInput form widget, intended for use with form fields which represent passwords, accepts a boolean keyword argument render_value indicating whether to send its data back to the browser when displaying a submitted form with errors.

Release notes Django 1.3.6 release notes

Previous versions of Django did not validate or limit the form-count data provided by the client in a formset’s management form, making it possible to exhaust a server’s available memory by forcing it to create very large numbers of forms.