The base view class from which most custom contact-form views should inherit. If you don’t need any custom functionality, and are content with the default
ContactFormclass, you can also just use it as-is (and the provided URLConf,
contact_form.urls, does exactly this).
This is a subclass of Django’s FormView, so refer to the Django documentation for a list of attributes/methods which can be overridden to customize behavior.
One non-standard attribute is defined here:
The list of email addresses to send mail to. If not specified, defaults to the
recipient_listof the form.
Additionally, the following standard (from
FormView) methods and attributes are commonly useful to override (all attributes below can also be passed to
as_view()in the URLconf, permitting customization without the need to write a full custom subclass of
The form class to use. By default, will be
ContactForm. This can also be overridden as a method named
form_class(); this permits, for example, per-request customization (by inspecting attributes of
The template to use when rendering the form. By default, will be
The URL to redirect to after successful form submission. By default, this is the named URL
contact_form.sent. In the default URLconf provided with django-contact-form, that URL is mapped to
TemplateViewrendering the template
Returns additional keyword arguments (as a dictionary) to pass to the form class on initialization.
By default, this will return a dictionary containing the current
HttpRequest(as the key
request) and, if
recipient_listwas defined, its value (as the key
If you override
get_form_kwargs(), you must ensure that, at the very least, the keyword argument
requestis still provided, or
ContactForminitialization will raise
TypeError. The simplest approach is to use
super()to call the base implementation in
ContactFormView, and modify the dictionary it returns.
To work around a potential performance issue in Django 1.9,
form_invalid()method. If you choose to override
form_invalid()in a subclass of
ContactFormView, be sure to read the implementation and comments in the source code of django-contact-form first. Note that Django 1.9.1, once released, will not be affected by this bug.