Messages framework for flash messages in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Django template snippet?

Given the following Django template code that uses the messages framework, what will be rendered if there is one message with level 'info' and text 'Welcome back!'?

Django

{% if messages %}
<ul>
  {% for message in messages %}
    <li>{{ message.level_tag }}: {{ message }}</li>
  {% endfor %}
</ul>
{% else %}
<p>No messages</p>
{% endif %}

A <ul><li>Info: Welcome back!</li></ul>

B <ul><li>info: Welcome back!</li></ul>

C <p>No messages</p>

D <ul><li>INFO: Welcome back!</li></ul>

💡 Hint

Remember that message.level_tag is lowercase by default.

The messages framework provides message.level_tag in lowercase, so 'info' is rendered exactly as 'info'. The message text is 'Welcome back!'.

📝 Syntax

intermediate

Which option correctly adds a success message in a Django view?

You want to add a success flash message in a Django view function. Which code snippet correctly does this?

Django

from django.contrib import messages

def my_view(request):
    # Add success message here
    pass

A messages.add('success', request, 'Operation completed successfully!')

B messages.add_message('success', request, 'Operation completed successfully!')

C messages.success('Operation completed successfully!', request)

D messages.success(request, 'Operation completed successfully!')

💡 Hint

Check the order of arguments in the messages.success function.

The correct syntax is messages.success(request, message_text). The request object must be the first argument.

🔧 Debug

advanced

Why does this Django view not display any flash messages?

Consider this Django view code: from django.contrib import messages def my_view(request): messages.error(request, 'An error occurred') return render(request, 'my_template.html') The template uses the standard messages loop. Why might no message appear?

Django

from django.contrib import messages
from django.shortcuts import render

def my_view(request):
    messages.error(request, 'An error occurred')
    return render(request, 'my_template.html')

A The messages middleware is missing from settings.py.

B The messages.error function is deprecated and does not add messages.

C The messages framework requires a redirect after adding messages to display them.

D The template must include {% load messages %} to show messages.

💡 Hint

Check if the messages middleware is enabled in the Django settings.

If the messages middleware is missing, messages won't be stored or passed to the template, so no messages appear.

❓ state_output

advanced

What is the value of messages after this code runs?

Given this Django view code snippet: from django.contrib import messages def my_view(request): messages.info(request, 'Info 1') messages.warning(request, 'Warning 1') messages.info(request, 'Info 2') What will be the count of messages stored for the current request?

Django

from django.contrib import messages

def my_view(request):
    messages.info(request, 'Info 1')
    messages.warning(request, 'Warning 1')
    messages.info(request, 'Info 2')

A 1

B 2

C 3

D 0

💡 Hint

Each call to messages adds one message to the storage.

Each call to messages.info or messages.warning adds one message, so total is 3.

🧠 Conceptual

expert

Which statement about Django's messages framework is TRUE?

Select the true statement about how Django's messages framework works.

A Messages are stored in the session by default and require session middleware.

B Messages are stored only in cookies and do not require any middleware.

C Messages are immediately removed after rendering the template, so they cannot be accessed twice.

D Messages require a database table to store messages between requests.

💡 Hint

Think about how messages persist between requests.

By default, Django stores messages in the session, so session middleware is required to use messages.