1293 sections across all versions Narrow to Django 6.0 (current) →
Release notes Django 4.2.1 release notes
Uploading multiple files using one form field has never been supported by forms.FileField or forms.ImageField as only the last uploaded file was validated. Unfortunately, Uploading multiple files topic suggested otherwise.
Release notes Django 3.2.19 release notes
Uploading multiple files using one form field has never been supported by forms.FileField or forms.ImageField as only the last uploaded file was validated. Unfortunately, Uploading multiple files topic suggested otherwise.
Release notes Django 4.1.9 release notes
Uploading multiple files using one form field has never been supported by forms.FileField or forms.ImageField as only the last uploaded file was validated. Unfortunately, Uploading multiple files topic suggested otherwise.
Release notes Django 4.2.1 release notes
Uploading multiple files using one form field has never been supported by forms.FileField or forms.ImageField as only the last uploaded file was validated. Unfortunately, Uploading multiple files topic suggested otherwise.
Release notes Django 1.7 release notes
Previously there were two main patterns for handling errors in forms: Raising a ValidationError from within certain functions (e.g.
Release notes Django 1.7 release notes What’s new in Django 1.7Improvements to Form error handling
Previously there were two main patterns for handling errors in forms: Raising a ValidationError from within certain functions (e.g.
Release notes Django 1.2 release notes
Model instances now have support for validating their own data, and both model and form fields now accept configurable lists of validators specifying reusable, encapsulated validation behavior. Note, however, that validation must still be performed explicitly.
Release notes Django 1.2 release notes What’s new in Django 1.2
Model instances now have support for validating their own data, and both model and form fields now accept configurable lists of validators specifying reusable, encapsulated validation behavior. Note, however, that validation must still be performed explicitly.
Release notes Django 1.7 release notes
The behavior of the ValidationError constructor has changed when it receives a container of errors as an argument (e.g.
Release notes Django 1.7 release notes Backwards incompatible changes in 1.7
The behavior of the ValidationError constructor has changed when it receives a container of errors as an argument (e.g.
Release notes Django 4.2.18 release notes
Lack of upper bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack.
Release notes Django 5.0.11 release notes
Lack of upper bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack.
Release notes Django 5.1.5 release notes
Lack of upper bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack.
Release notes Django 4.2.18 release notes
Lack of upper bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack.
Release notes Django 5.0.11 release notes
Lack of upper bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack.
Release notes Django 5.1.5 release notes
Lack of upper bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack.
Release notes Django 1.10 release notes
Form and widget Media is now served using django.contrib.staticfiles if installed. The <input> tag rendered by CharField now includes a minlength attribute if the field has a min_length. Required form fields now have the required HTML attribute.
Release notes Django 1.10 release notes What’s new in Django 1.10Minor features
Form and widget Media is now served using django.contrib.staticfiles if installed. The <input> tag rendered by CharField now includes a minlength attribute if the field has a min_length. Required form fields now have the required HTML attribute.
Release notes Django 1.7 release notes What’s new in Django 1.7Improvements to Form error handling
The ValidationError constructor accepts metadata such as error code or params which are then available for interpolating into the error message (see Raising ValidationError for more details); however, before Django 1.7 those metadata were discarded as soon as the errors …
Release notes Django 1.7 release notes
The ValidationError constructor accepts metadata such as error code or params which are then available for interpolating into the error message (see Raising ValidationError for more details); however, before Django 1.7 those metadata were discarded as soon as the errors …