The messages framework

Quite commonly in web applications, you need to display a one-timenotification message (also known as "flash message") to the user afterprocessing a form or some other types of user input.

For this, Django provides full support for cookie- and session-basedmessaging, for both anonymous and authenticated users. The messages frameworkallows you to temporarily store messages in one request and retrieve them fordisplay in a subsequent request (usually the next one). Every message istagged with a specific level that determines its priority (e.g., info,warning, or error).

Enabling messages

Messages are implemented through a middlewareclass and corresponding context processor.

The default settings.py created by django-admin startprojectalready contains all the settings required to enable message functionality:

• 'django.contrib.messages' is in INSTALLED_APPS.

• MIDDLEWARE contains'django.contrib.sessions.middleware.SessionMiddleware' and'django.contrib.messages.middleware.MessageMiddleware'.

The default storage backend relies onsessions. That's why SessionMiddlewaremust be enabled and appear before MessageMiddleware inMIDDLEWARE.

• The 'context_processors' option of the DjangoTemplates backenddefined in your TEMPLATES setting contains'django.contrib.messages.context_processors.messages'.

If you don't want to use messages, you can remove'django.contrib.messages' from your INSTALLED_APPS, theMessageMiddleware line from MIDDLEWARE, and the messagescontext processor from TEMPLATES.

Configuring the message engine

Storage backends

The messages framework can use different backends to store temporary messages.

Django provides three built-in storage classes indjango.contrib.messages:

• class storage.session.SessionStorage

• This class stores all messages inside of the request's session. Thereforeit requires Django's contrib.sessions application.

• class storage.cookie.CookieStorage

• This class stores the message data in a cookie (signed with a secret hashto prevent manipulation) to persist notifications across requests. Oldmessages are dropped if the cookie data size would exceed 2048 bytes.

• class storage.fallback.FallbackStorage

• This class first uses CookieStorage, and falls back to usingSessionStorage for the messages that could not fit in a single cookie.It also requires Django's contrib.sessions application.

This behavior avoids writing to the session whenever possible. It shouldprovide the best performance in the general case.

FallbackStorage is thedefault storage class. If it isn't suitable to your needs, you can selectanother storage class by setting MESSAGE_STORAGE to its full importpath, for example:

MESSAGE_STORAGE = 'django.contrib.messages.storage.cookie.CookieStorage'

• class storage.base.BaseStorage
• To write your own storage class, subclass the BaseStorage class indjango.contrib.messages.storage.base and implement the _get and_store methods.

Message levels

The messages framework is based on a configurable level architecture similarto that of the Python logging module. Message levels allow you to groupmessages by type so they can be filtered or displayed differently in views andtemplates.

The built-in levels, which can be imported from django.contrib.messagesdirectly, are:

The MESSAGE_LEVEL setting can be used to change the minimum recorded level(or it can be changed per request). Attempts to add messages of a level lessthan this will be ignored.

Message tags

Message tags are a string representation of the message level plus anyextra tags that were added directly in the view (seeAdding extra message tags below for more details). Tags are stored in astring and are separated by spaces. Typically, message tagsare used as CSS classes to customize message style based on message type. Bydefault, each level has a single tag that's a lowercase version of its ownconstant:

To change the default tags for a message level (either built-in or custom),set the MESSAGE_TAGS setting to a dictionary containing the levelsyou wish to change. As this extends the default tags, you only need to providetags for the levels you wish to override:

from django.contrib.messages import constants as messages
MESSAGE_TAGS = {
    messages.INFO: '',
    50: 'critical',
}

Using messages in views and templates

• addmessage(_request, level, message, extra_tags='', fail_silently=False)[源代码]

Adding a message

To add a message, call:

from django.contrib import messages
messages.add_message(request, messages.INFO, 'Hello world.')

Some shortcut methods provide a standard way to add messages with commonlyused tags (which are usually represented as HTML classes for the message):

messages.debug(request, '%s SQL statements were executed.' % count)
messages.info(request, 'Three credits remain in your account.')
messages.success(request, 'Profile details updated.')
messages.warning(request, 'Your account expires in three days.')
messages.error(request, 'Document deleted.')

Displaying messages

• getmessages(_request)[源代码]
• In your template, use something like:

{% if messages %}
<ul class="messages">
    {% for message in messages %}
    <li{% if message.tags %} class="{{ message.tags }}"{% endif %}>{{ message }}</li>
    {% endfor %}
</ul>
{% endif %}

If you're using the context processor, your template should be rendered with aRequestContext. Otherwise, ensure messages is available tothe template context.

Even if you know there is only just one message, you should still iterate overthe messages sequence, because otherwise the message storage will not be clearedfor the next request.

The context processor also provides a DEFAULT_MESSAGE_LEVELS variable whichis a mapping of the message level names to their numeric value:

{% if messages %}
<ul class="messages">
    {% for message in messages %}
    <li{% if message.tags %} class="{{ message.tags }}"{% endif %}>
        {% if message.level == DEFAULT_MESSAGE_LEVELS.ERROR %}Important: {% endif %}
        {{ message }}
    </li>
    {% endfor %}
</ul>
{% endif %}

Outside of templates, you can useget_messages():

from django.contrib.messages import get_messages
 
storage = get_messages(request)
for message in storage:
    do_something_with_the_message(message)

For instance, you can fetch all the messages to return them in aJSONResponseMixin instead of aTemplateResponseMixin.

get_messages() will return aninstance of the configured storage backend.

The Message class

• class storage.base.Message

• When you loop over the list of messages in a template, what you get areinstances of the Message class. It's quite a simple object, with only afew attributes:

  • message: The actual text of the message.
  • level: An integer describing the type of the message (see themessage levels section above).
  • tags: A string combining all the message's tags (extra_tags andlevel_tag) separated by spaces.
  • extra_tags: A string containing custom tags for this message,separated by spaces. It's empty by default.
  • level_tag: The string representation of the level. By default, it'sthe lowercase version of the name of the associated constant, but thiscan be changed if you need by using the MESSAGE_TAGS setting.

Creating custom message levels

Messages levels are nothing more than integers, so you can define your ownlevel constants and use them to create more customized user feedback, e.g.:

CRITICAL = 50
 
def my_view(request):
    messages.add_message(request, CRITICAL, 'A serious error occurred.')

When creating custom message levels you should be careful to avoid overloadingexisting levels. The values for the built-in levels are:

If you need to identify the custom levels in your HTML or CSS, you need toprovide a mapping via the MESSAGE_TAGS setting.

注解

If you are creating a reusable application, it is recommended to useonly the built-in message levels and not rely on any custom levels.

Changing the minimum recorded level per-request

The minimum recorded level can be set per request via the set_levelmethod:

from django.contrib import messages
 
# Change the messages level to ensure the debug message is added.
messages.set_level(request, messages.DEBUG)
messages.debug(request, 'Test message...')
 
# In another request, record only messages with a level of WARNING and higher
messages.set_level(request, messages.WARNING)
messages.success(request, 'Your profile was updated.') # ignored
messages.warning(request, 'Your account is about to expire.') # recorded
 
# Set the messages level back to default.
messages.set_level(request, None)

Similarly, the current effective level can be retrieved with get_level:

from django.contrib import messages
current_level = messages.get_level(request)

For more information on how the minimum recorded level functions, seeMessage levels above.

Adding extra message tags

For more direct control over message tags, you can optionally provide a stringcontaining extra tags to any of the add methods:

messages.add_message(request, messages.INFO, 'Over 9000!', extra_tags='dragonball')
messages.error(request, 'Email box full', extra_tags='email')

Extra tags are added before the default tag for that level and are spaceseparated.

Failing silently when the message framework is disabled

If you're writing a reusable app (or other piece of code) and want to includemessaging functionality, but don't want to require your users to enable itif they don't want to, you may pass an additional keyword argumentfail_silently=True to any of the add_message family of methods. Forexample:

messages.add_message(
    request, messages.SUCCESS, 'Profile details updated.',
    fail_silently=True,
)
messages.info(request, 'Hello world.', fail_silently=True)

注解

Setting fail_silently=True only hides the MessageFailure that wouldotherwise occur when the messages framework disabled and one attempts touse one of the add_message family of methods. It does not hide failuresthat may occur for other reasons.

Adding messages in class-based views

• class views.SuccessMessageMixin

• Adds a success message attribute toFormView based classes

  • getsuccess_message(_cleaned_data)
  • cleaned_data is the cleaned data from the form which is used forstring formatting

Example views.py:

from django.contrib.messages.views import SuccessMessageMixin
from django.views.generic.edit import CreateView
from myapp.models import Author
 
class AuthorCreate(SuccessMessageMixin, CreateView):
    model = Author
    success_url = '/success/'
    success_message = "%(name)s was created successfully"

The cleaned data from the form is available for string interpolation usingthe %(field_name)s syntax. For ModelForms, if you need access to fieldsfrom the saved object override theget_success_message()method.

Example views.py for ModelForms:

from django.contrib.messages.views import SuccessMessageMixin
from django.views.generic.edit import CreateView
from myapp.models import ComplicatedModel
 
class ComplicatedCreate(SuccessMessageMixin, CreateView):
    model = ComplicatedModel
    success_url = '/success/'
    success_message = "%(calculated_field)s was created successfully"
 
    def get_success_message(self, cleaned_data):
        return self.success_message % dict(
            cleaned_data,
            calculated_field=self.object.calculated_field,
        )

Expiration of messages

The messages are marked to be cleared when the storage instance is iterated(and cleared when the response is processed).

To avoid the messages being cleared, you can set the messages storage toFalse after iterating:

storage = messages.get_messages(request)
for message in storage:
    do_something_with(message)
storage.used = False

Behavior of parallel requests

Due to the way cookies (and hence sessions) work, the behavior of anybackends that make use of cookies or sessions is undefined when the sameclient makes multiple requests that set or get messages in parallel. Forexample, if a client initiates a request that creates a message in one window(or tab) and then another that fetches any uniterated messages in anotherwindow, before the first window redirects, the message may appear in thesecond window instead of the first window where it may be expected.

In short, when multiple simultaneous requests from the same client areinvolved, messages are not guaranteed to be delivered to the same window thatcreated them nor, in some cases, at all. Note that this is typically not aproblem in most applications and will become a non-issue in HTML5, where eachwindow/tab will have its own browsing context.

Settings

A few settings give you control over messagebehavior:

• MESSAGE_LEVEL
• MESSAGE_STORAGE

• MESSAGE_TAGS
  For backends that use cookies, the settings for the cookie are taken fromthe session cookie settings:

• SESSION_COOKIE_DOMAIN

• SESSION_COOKIE_SECURE
• SESSION_COOKIE_HTTPONLY