Topic guide Working with forms

dev

Topic guide Working with forms

dev

Topic guide Working with forms

All form classes are created as subclasses of either django.forms.Form or django.forms.ModelForm. You can think of ModelForm as a subclass of Form.

dev

Topic guide Working with forms

The distinction between Bound and unbound forms is important: An unbound form has no data associated with it. When rendered to the user, it will be empty or will contain default values.

dev

Topic guide Working with forms

All you need to do to get your form into a template is to place the form instance into the template context.

dev

How-to How to create custom model fields Writing a field subclassUseful methods

To customize the form field used by ModelForm, you can override formfield(). The form field class can be specified via the form_class and choices_form_class arguments; the latter is used if the field has choices specified, the former otherwise.

4.2 5.0 5.1 5.2 6.0

Tutorial Writing your first Django app, part 4

Let’s update our poll detail template (“polls/detail.html”) from the last tutorial, so that the template contains an HTML <form> element: polls/templates/polls/detail.html A quick rundown: The above template displays a radio button for each question choice.

4.2 5.0 5.1 5.2 6.0

Tutorial Writing your first Django app, part 7

By registering the Question model with admin.site.register(Question), Django was able to construct a default form representation. Often, you’ll want to customize how the admin form looks and works.

4.2 5.0 5.1 5.2 6.0

Reference

All of these fields and widgets are available from the django.contrib.postgres.forms module.

4.2 5.0 5.1 5.2 6.0

Reference The Forms API

Form.has_changed() Use the has_changed() method on your Form when you need to check if the form data has been changed from the initial data.

4.2 5.0 5.1 5.2 6.0

Reference The Forms API Outputting forms as HTML

Form.error_css_class Form.required_css_class It’s pretty common to style form rows and fields that are required or have errors. For example, you might want to present required form rows in bold and highlight errors in red.

4.2 5.0 5.1 5.2 6.0

Topic guide Working with forms

4.2 5.0 5.1 5.2 6.0

Topic guide Working with forms Building a form

4.2 5.0 5.1 5.2 6.0

Topic guide Working with forms

All form classes are created as subclasses of either django.forms.Form or django.forms.ModelForm. You can think of ModelForm as a subclass of Form.

4.2 5.0 5.1 5.2 6.0

Topic guide Working with forms More about Django Form classes

The distinction between Bound and unbound forms is important: An unbound form has no data associated with it. When rendered to the user, it will be empty or will contain default values.

4.2 5.0 5.1 5.2 6.0

Topic guide Working with forms

All you need to do to get your form into a template is to place the form instance into the template context.

4.2 5.0 5.1 5.2 6.0

Reference The Forms API

Form.fields You can access the fields of Form instance from its fields attribute: You can alter the field and BoundField of Form instance to change the way it is presented in the form: Beware not to alter the base_fields attribute …

dev

Reference The Forms API

Form.default_renderer Specifies the renderer to use for the form. Defaults to None which means to use the default renderer specified by the FORM_RENDERER setting.

dev

Reference The Forms API

Dealing with forms that have FileField and ImageField fields is a little more complicated than a normal form.

dev

Topic guide Creating forms from models

Using the widgets parameter, you can specify a dictionary of values to customize the ModelForm’s widget class for a particular field. This works the same way as the widgets dictionary on the inner Meta class of a ModelForm works:

dev