Reference The form rendering API
BaseFormSet.template_name To override formset templates, you must use the TemplatesSetting renderer. Then overriding formset templates works the same as overriding any other template in your project.
711 sections in Django dev Search all versions →
Reference The form rendering API
BaseFormSet.template_name To override formset templates, you must use the TemplatesSetting renderer. Then overriding formset templates works the same as overriding any other template in your project.
Reference The form rendering API
Field.template_name To override field templates, you must use the TemplatesSetting renderer. Then overriding field templates works the same as overriding any other template in your project.
Reference The form rendering API
Built-in widget templates are stored in the django/forms/widgets path. You can provide a custom template for input.html by defining django/forms/templates/django/forms/widgets/input.html, for example. See Built-in widgets for the name of each widget’s template.
Reference PostgreSQL specific form fields and widgets
This group of fields all share similar functionality for accepting range data. They are based on MultiValueField. They treat one omitted value as an unbounded range. They also validate that the lower bound is not greater than the upper bound.
Reference PostgreSQL specific form fields and widgets
classIntegerRangeField : Based on IntegerField and translates its input into django.db.backends.postgresql.psycopg_any.NumericRange. Default for IntegerRangeField and BigIntegerRangeField.
Reference PostgreSQL specific form fields and widgets
classDecimalRangeField : Based on DecimalField and translates its input into django.db.backends.postgresql.psycopg_any.NumericRange. Default for DecimalRangeField.
Reference PostgreSQL specific form fields and widgets
classDateTimeRangeField : Based on DateTimeField and translates its input into django.db.backends.postgresql.psycopg_any.DateTimeTZRange. Default for DateTimeRangeField.
Reference PostgreSQL specific form fields and widgets
classDateRangeField : Based on DateField and translates its input into django.db.backends.postgresql.psycopg_any.DateRange. Default for DateRangeField.
Reference PostgreSQL specific form fields and widgets
classRangeWidget(base_widget,attrs=None) : Widget used by all of the range fields. Based on MultiWidget.
Release notes Django 2.0 release notes
To help prevent runtime errors due to incorrect ordering of form field arguments, optional arguments of built-in form fields are no longer accepted as positional arguments. For example: raises an exception and should be replaced with:
Release notes Django 4.1 release notes
In order to aid users with screen readers, and other assistive technology, new <div> based form templates are available from this release.
Release notes Django 1.4 release notes
The previous FormWizard from django.contrib.formtools has been replaced with a new implementation based on the class-based views introduced in Django 1.3.
Release notes Django 1.5 release notes
request.POST will no longer include data posted via HTTP requests with non form-specific content-types in the header. In prior versions, data posted with content-types other than multipart/form-data or application/x-www-form-urlencoded would still end up represented in the request.POST attribute.
Release notes Django 1.6 release notes
GeoDjango now provides form fields and widgets for its geo-specialized fields. They are OpenLayers-based by default, but they can be customized to use any other JS framework.
Release notes Django 1.6 release notes
HTML rendering of model form fields corresponding to ManyToManyField model fields used to get the hardcoded sentence: Hold down “Control”, or “Command” on a Mac, to select more than one.
Release notes Django 1.7 release notes
Release notes Django 2.2 release notes
Form Media assets are now merged using a topological sort algorithm, as the old pairwise merging algorithm is insufficient for some cases.
Release notes Django 4.0 release notes
Forms, Formsets, and ErrorList are now rendered using the template engine to enhance customization. See the new render(), get_context(), and template_name for Form and formset rendering for Formset.