Form error handling in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if the form has errors.

Django

if form.[1]:
    print("Form has errors")

Drag options to blanks, or click blank then click option'

Ais_valid

Bis_error

Cerrors

Dhas_errors

Attempts:

3 left

💡 Hint

Common Mistakes

Using form.is_valid() to check errors (it returns True if no errors).

Trying to call a non-existent method like form.has_errors().

The form.errors attribute returns a dictionary of errors if the form has any. Checking it directly tells if there are errors.

2fill in blank

medium

Complete the code to display non-field errors in a Django template.

Django

{% if form.[1] %}
  <ul>
  {% for error in form.[1] %}
    <li>{{ error }}</li>
  {% endfor %}
  </ul>
{% endif %}

Drag options to blanks, or click blank then click option'

Anon_field_errors

Ball_errors

Cfield_errors

Derrors

Attempts:

3 left

💡 Hint

Common Mistakes

Using form.errors which iterates over field names, not messages.

Trying to use a non-existent attribute like all_errors.

In Django templates, form.non_field_errors is an ErrorList containing non-field errors for the form. It can be iterated to display messages.

3fill in blank

hard

Fix the error in the code to add a custom error to a form field.

Django

def clean_username(self):
    username = self.cleaned_data.get('username')
    if username == 'admin':
        self.[1]('username', 'This username is not allowed.')
    return username

Drag options to blanks, or click blank then click option'

Aset_error

Braise_error

Cerror_add

Dadd_error

Attempts:

3 left

💡 Hint

Common Mistakes

Using raise_error which is not a form method.

Trying to set errors by assigning directly to a field.

The add_error method adds an error message to a specific field in the form.

4fill in blank

hard

Fill both blanks to check if the form is valid and then access the errors.

Django

if form.[1]():
    print(form.[2])

Drag options to blanks, or click blank then click option'

Ais_valid

Bis_error

Cerrors

Dhas_errors

Attempts:

3 left

💡 Hint

Common Mistakes

Using is_error() which does not exist.

Trying to access errors before checking validity.

First, form.is_valid() checks if the form data is valid. form.errors contains the error details if invalid (empty dict if valid).

5fill in blank

hard

Fill all three blanks to add a non-field error and then check if the form has any errors.

Django

form.[1](None, '[2]')
if form.[3]:
    print('There are errors')

Drag options to blanks, or click blank then click option'

Aadd_error

BThis is a non-field error

Cerrors

Dis_valid

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a field name instead of None for non-field errors.

Checking is_valid instead of errors to detect errors.

Use add_error(None, message) to add a non-field error. Then check form.errors to see if any errors exist.

Practice

1. What does form.is_valid() do in Django form handling?

easy

A. Saves the form data to the database automatically

B. Checks if the submitted form data meets all validation rules

C. Clears all errors from the form

D. Displays the form errors to the user

Solution

1. Step 1: Understand the purpose of form.is_valid()

   This method checks if the form data passes all validation checks defined in the form.

2. Step 2: Differentiate from other form methods

   It does not save data or clear errors; it only returns True if data is valid, False otherwise.

3. Final Answer:

   Checks if the submitted form data meets all validation rules -> Option B

4. Quick Check:

   form.is_valid() = validation check [OK]

Hint: Remember: is_valid() only checks data correctness [OK]

Common Mistakes:

• Thinking is_valid() saves data
• Confusing is_valid() with error display
• Assuming is_valid() clears errors

2. Which of the following is the correct way to access form errors in a Django template?

easy

A. {{ form.errors }}

B. {{ form.error_list }}

C. {{ form.error_messages }}

D. {{ form.error }}

Solution

1. Step 1: Recall Django form error attribute

   The correct attribute to access errors is form.errors, which returns a dictionary of errors.

2. Step 2: Verify template syntax

   Using {{ form.errors }} in the template displays the errors properly.

3. Final Answer:

   {{ form.errors }} -> Option A

4. Quick Check:

   Use form.errors to show errors [OK]

Hint: Use form.errors to get all errors in templates [OK]

Common Mistakes:

• Using non-existent attributes like error_list
• Trying to access errors with singular 'error'
• Confusing error_messages with errors

3. Given this Django form code snippet, what will print(form.errors) output if the 'email' field is left empty?

class ContactForm(forms.Form):
    email = forms.EmailField(required=True)

form = ContactForm(data={'email': ''})
form.is_valid()
print(form.errors)

medium

A. {'email': ['This field is required.']}

B. {}

C. {'email': ['Enter a valid email address.']}

D. None

Solution

1. Step 1: Understand required field behavior

   The 'email' field is required, so leaving it empty triggers a 'This field is required.' error.

2. Step 2: Check form.errors output

   After calling form.is_valid(), form.errors contains the error message for the empty 'email' field.

3. Final Answer:

   {'email': ['This field is required.']} -> Option A

4. Quick Check:

   Empty required field = 'This field is required.' error [OK]

Hint: Empty required fields always add 'This field is required.' error [OK]

Common Mistakes:

• Expecting empty errors dictionary
• Confusing empty with invalid email format error
• Assuming errors is None when invalid

4. Identify the error in this Django form handling code snippet:

form = MyForm(request.POST)
if form.is_valid:
    form.save()

medium

A. Using form.save() without checking is_valid

B. Form instance should be created with request.FILES

C. request.POST should be request.GET

D. Missing parentheses after is_valid method call

Solution

1. Step 1: Check method call syntax

   The code uses form.is_valid without parentheses, so it references the method but does not call it.

2. Step 2: Understand consequences

   This means the if condition always evaluates to True because the method itself is truthy, causing potential errors.

3. Final Answer:

   Missing parentheses after is_valid method call -> Option D

4. Quick Check:

   Call is_valid() with () to check validity [OK]

Hint: Always add () to call is_valid method [OK]

Common Mistakes:

• Forgetting parentheses on is_valid
• Assuming is_valid is a property
• Mixing request.POST with request.GET incorrectly

5. You want to display individual error messages next to each form field in your Django template. Which template code snippet correctly achieves this?

hard

A. {{ form.errors }}

B. {% for error in form.errors %}
{{ error }}
{% endfor %}

C. {% for field in form %}
{{ field.label }}
{{ field }}
{% for error in field.errors %}
{{ error }}
{% endfor %}
{% endfor %}

D. {% if form.errors %}
There are errors in the form.
{% endif %}

Solution

1. Step 1: Understand error display per field

   To show errors next to each field, iterate over form fields and then over each field's errors.

2. Step 2: Analyze each option

   {% for field in form %} {{ field.label }} {{ field }} {% for error in field.errors %} {{ error }} {% endfor %} {% endfor %} loops over fields and their errors, displaying them properly. Using {{ form.errors }} or {% for error in form.errors %} shows all errors together, not per field. {% if form.errors %}

   There are errors in the form.

   {% endif %} only shows a message if errors exist, no details.

3. Final Answer:

   {% for field in form %} {{ field.label }} {{ field }} {% for error in field.errors %} {{ error }} {% endfor %} {% endfor %} -> Option C

4. Quick Check:

   Loop fields and field.errors for per-field messages [OK]

Hint: Loop fields and field.errors to show errors per field [OK]

Common Mistakes:

• Showing all errors together without field context
• Not looping over field.errors
• Only showing generic error message