djangodocs.org

711 sections in Django dev Search all versions →

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.

Range Fields

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.

New form wizard

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.

GeoDjango form widgets

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 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.