from django.conf import settings
from django.core.mail import send_mail
-from django.template import loader, RequestContext
+from django.template import loader
+from django.template import RequestContext
from django.contrib.sites.models import Site
Base contact form class from which all contact form classes should
If you don't need any custom functionality, you can simply use
this form to provide basic contact functionality; it will collect
name, email address and message.
The ``contact_form`` view included in this application knows how
to work with this form and can handle many types of subclasses as
well (see below for a discussion of the important points), so in
many cases it will be all that you need. If you'd like to use this
form or a subclass of it from one of your own views, just do the
- 1. When you instantiate the form, pass the current
- ``HttpRequest`` object to the constructor as the keyword
- argument ``request``; this is used internally by the base
- implementation, and also made available so that subclasses
- can add functionality which relies on inspecting the
- 2. To send the message, call the form's ``save`` method, which
- accepts the keyword argument ``fail_silently`` and defaults
- it to ``False``. This argument is passed directly to
- ``send_mail``, and allows you to suppress or raise
- exceptions as needed for debugging. The ``save`` method has
+ 1. When you instantiate the form, pass the current ``HttpRequest``
+ object to the constructor as the keyword argument ``request``;
+ this is used internally by the base implementation, and also
+ made available so that subclasses can add functionality which
+ relies on inspecting the request.
+ 2. To send the message, call the form's ``save`` method, which
+ accepts the keyword argument ``fail_silently`` and defaults it
+ to ``False``. This argument is passed directly to
+ ``send_mail``, and allows you to suppress or raise exceptions
+ as needed for debugging. The ``save`` method has no return
Other than that, treat it like any other form; validity checks and
validated data are handled normally, through the ``is_valid``
method and the ``cleaned_data`` dictionary.
Under the hood, this form uses a somewhat abstracted interface in
order to make it easier to subclass and add functionality. There
are several important attributes subclasses may want to look at
overriding, all of which will work (in the base implementation) as
either plain attributes or as callable methods:
- * ``from_email`` -- used to get the address to use in the
- ``From:`` header of the message. The base implementation
- returns the value of the ``DEFAULT_FROM_EMAIL`` setting.
- * ``message`` -- used to get the message body as a string. The
- base implementation renders a template using the form's
- ``cleaned_data`` dictionary as context.
- * ``recipient_list`` -- used to generate the list of
- recipients for the message. The base implementation returns
- the email addresses specified in the ``MANAGERS`` setting.
- * ``subject`` -- used to generate the subject line for the
- message. The base implementation returns the string 'Message
- sent through the web site', with the name of the current
- * ``template_name`` -- used by the base ``message`` method to
- determine which template to use for rendering the
- message. Default is ``contact_form/contact_form.txt``.
+ * ``from_email`` -- used to get the address to use in the
+ ``From:`` header of the message. The base implementation returns
+ the value of the ``DEFAULT_FROM_EMAIL`` setting.
+ * ``message`` -- used to get the message body as a string. The
+ base implementation renders a template using the form's
+ ``cleaned_data`` dictionary as context.
+ * ``recipient_list`` -- used to generate the list of recipients
+ for the message. The base implementation returns the email
+ addresses specified in the ``MANAGERS`` setting.
+ * ``subject`` -- used to generate the subject line for the
+ message. The base implementation returns the string 'Message
+ sent through the web site', with the name of the current
+ * ``template_name`` -- used by the base ``message`` method to
+ determine which template to use for rendering the
+ message. Default is ``contact_form/contact_form.txt``.
Internally, the base implementation ``_get_message_dict`` method
collects ``from_email``, ``message``, ``recipient_list`` and
``subject`` into a dictionary, which the ``save`` method then
passes directly to ``send_mail`` as keyword arguments.
Particularly important is the ``message`` attribute, with its base
implementation as a method which renders a template; because it
passes ``cleaned_data`` as the template context, any additional
template. This means that many useful subclasses can get by with
just adding a few fields and possibly overriding
Much useful functionality can be achieved in subclasses without
having to override much of the above; adding additional validation
methods works the same as any other form, and typically only a few
items -- ``recipient_list`` and ``subject_line``, for example,
need to be overridden to achieve customized behavior.
Other notes for subclassing
Subclasses which want to inspect the current ``HttpRequest`` to
add functionality can access it via the attribute ``request``; the
base ``message`` takes advantage of this to use ``RequestContext``
when rendering its template. See the ``AkismetContactForm``
subclass in this file for an example of using the request to
perform additional validation.
Subclasses which override ``__init__`` need to accept ``*args``
and ``**kwargs``, and pass them via ``super`` in order to ensure
Subclasses should be careful if overriding ``_get_message_dict``,
since that method **must** return a dictionary suitable for
passing directly to ``send_mail`` (unless ``save`` is overridden
Overriding ``save`` is relatively safe, though remember that code
which uses your form will expect ``save`` to accept the
``fail_silently`` keyword argument. In the base implementation,
s the body of the message to a string.
+ Render the body of the message to a string.
s the subject of the message to a string.
+ Render the subject of the message to a string.
subject = loader.render_to_string(self.subject_template_name,
+ Return the context used to render the templates for the email
+ By default, this context includes:
+ * All of the validated values in the form, as variables of the
+ same names as their fields.
+ * The current ``Site`` object, as the variable ``site``.
+ * Any additional variables added by context processors (this
+ will be a ``RequestContext``).
raise ValueError("Cannot generate Context from invalid contact form")
+ Generate the various parts of the message and return them in a
+ dictionary, suitable for passing directly as keyword arguments
+ to ``django.core.mail.send_mail()``.
+ By default, the following values are returned:
raise ValueError("Message cannot be sent from invalid contact form")
def save(self, fail_silently=False):
s and send s the email message.
+ Build and send the email message.
Contact form which doesn't add any extra fields, but does add an
Akismet spam check to the validation routine.
Requires the setting ``AKISMET_API_KEY``, which should be a valid
+ Perform Akismet validation of the message.
if 'body' in self.cleaned_data and getattr(settings, 'AKISMET_API_KEY', ''):
from akismet import Akismet
from django.utils.encoding import smart_str