Reference GeoDjango Forms API Form field classes

classGeometryCollectionField[source]

Reference Model forms Model form Meta API

ModelFormOptions.error_messages : A dictionary that maps a model field name to a dictionary of error message keys (null, blank, invalid, unique, etc.) mapped to custom error messages.

Reference Model forms Model form Meta API

ModelFormOptions.formfield_callback : A function or callable that takes a model field and returns a django.forms.Field object.

Reference Model forms Model form Meta API

ModelFormOptions.help_texts : A dictionary that maps a model field name to a help text string.

Reference Model forms Model form Meta API

ModelFormOptions.labels : A dictionary that maps a model field names to a label string.

Reference Model forms Model form Meta API

ModelFormOptions.model : Required. The django.db.models.Model to be used for the ModelForm.

Reference Model forms Model form Meta API

ModelFormOptions.widgets : A dictionary that maps a model field name to a django.forms.Widget.

Reference Model forms Model form factory functions

inlineformset_factory(parent_model,model,form=ModelForm,formset=BaseInlineFormSet,fk_name=None,fields=None,exclude=None,extra=3,can_order=False,can_delete=True,max_num=None,formfield_callback=None,widgets=None,validate_max=False,localized_fields=None,labels=None,help_texts=None,error_messages=None,min_num=None,validate_min=False,field_classes=None,absolute_max=None,can_delete_extra=True,renderer=None,edit_only=False)[source] : Returns an InlineFormSet using modelformset_factory() with defaults of formset=BaseInlineFormSet, can_delete=True, and extra=3.

Reference JavaScript customizations in the admin Inline form events

jQuery handles JavaScript events but the reverse isn’t true. You could check for the presence of event.detail.formsetName and fall back to the old listener signature as follows:

Release notes Django 2.0 release notes Backwards incompatible changes in 2.0

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 What’s new in Django 4.1

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 What’s new in Django 1.4

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 Backwards incompatible changes in 1.5

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 What’s new in Django 1.6

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 Backwards incompatible changes in 1.6

HTML rendering of model form fields corresponding to ManyToManyField model fields used to get the hard-coded sentence: Hold down “Control”, or “Command” on a Mac, to select more than one.

Release notes Django 1.7 release notes What’s new in Django 1.7

Release notes Django 2.2 release notes Backwards incompatible changes in 2.2

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 What’s new in Django 4.0

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.

Release notes Django 5.0 release notes What’s new in Django 5.0

Django 5.0 introduces the concept of a field group, and field group templates. This simplifies rendering of the related elements of a Django form field such as its label, widget, help text, and errors.

Release notes Django 1.6 release notes Backwards incompatible changes in 1.6

This is consistent with how methods like Form.as_p and Form.as_ul render labels.