Displaying forms in templates in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to display a form in a Django template.

Django

<form method="post">
  {% csrf_token %}
  {{ form.[1] }}
  <button type="submit">Submit</button>
</form>

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

Ashow

Brender

Cas_p

Ddisplay

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'render' or 'show' on the form object.

Forgetting to include the CSRF token.

Use as_p to render the form fields wrapped in paragraph tags for easy styling.

2fill in blank

medium

Complete the code to include the CSRF token in the form.

Django

<form method="post">
  [1]
  {{ form.as_p }}
  <button type="submit">Submit</button>
</form>

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

A{% csrf_token %}

B{% csrf %}

C{{ csrf_token }}

D{% token_csrf %}

Attempts:

3 left

💡 Hint

Common Mistakes

Using double curly braces instead of template tags.

Misspelling the tag name.

The correct tag to include CSRF protection in Django templates is {% csrf_token %}.

3fill in blank

hard

Fix the error in the template code to correctly display form errors.

Django

<form method="post">
  {% csrf_token %}
  {{ form.[1] }}
  <button type="submit">Submit</button>
</form>

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

Aerror_messages

Berror

Cerror_list

Derrors

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular 'error' which does not exist.

Trying to access non-existent attributes like 'error_list'.

The correct attribute to display form errors in Django templates is errors.

4fill in blank

hard

Fill both blanks to render the form fields as a table and include the submit button.

Django

<form method="post">
  {% csrf_token %}
  {{ form.[1] }}
  <button type="[2]">Submit</button>
</form>

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

Aas_table

Bsubmit

Cbutton

Dreset

Attempts:

3 left

💡 Hint

Common Mistakes

Using as_p instead of as_table when a table layout is needed.

Setting button type to button which does not submit the form.

Use as_table to render form fields in a table layout and set the button type to submit to send the form.

5fill in blank

hard

Fill all three blanks to display form fields as an unordered list, add a CSS class to the form, and set the button type.

Django

<form method="post" class="[1]">
  {% csrf_token %}
  {{ form.[2] }}
  <button type="[3]">Submit</button>
</form>

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

Aform-style

Bas_ul

Csubmit

Dform-class

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid CSS class names or missing the class attribute.

Using as_p or as_table instead of as_ul.

Setting button type to button or reset instead of submit.

Use form-class as the CSS class name, as_ul to render form fields as a list, and submit for the button type.

Practice

1. What is the purpose of using {% csrf_token %} in a Django form template?

easy

A. To protect the form from Cross-Site Request Forgery attacks

B. To style the form fields automatically

C. To submit the form data to the server

D. To display error messages for the form

Solution

1. Step 1: Understand CSRF protection in Django

   Django uses {% csrf_token %} to add a hidden token to forms that helps prevent malicious attacks from other sites.

2. Step 2: Identify the role of the token in form security

   This token is checked on form submission to ensure the request is from the original site, protecting against CSRF attacks.

3. Final Answer:

   To protect the form from Cross-Site Request Forgery attacks -> Option A

4. Quick Check:

   CSRF token = security protection [OK]

Hint: CSRF token always means security against fake form submissions [OK]

Common Mistakes:

• Thinking it styles the form
• Confusing it with form submission action
• Assuming it shows errors

2. Which of the following is the correct way to render a Django form as paragraphs in a template?

easy

A. {{ form.as_p }}

B. {{ form.as_table }}

C. {{ form.render() }}

D. {% form.as_p %}

Solution

1. Step 1: Recall Django form rendering methods

   Django forms have built-in methods like as_p, as_table, and as_ul to render fields in different HTML formats.

2. Step 2: Identify the correct syntax for paragraph rendering

   The correct syntax to render form fields wrapped in paragraphs is {{ form.as_p }}. The other options are either wrong methods or incorrect template syntax.

3. Final Answer:

   {{ form.as_p }} -> Option A

4. Quick Check:

   Render form as paragraphs = {{ form.as_p }} [OK]

Hint: Use {{ form.as_p }} to render form fields in paragraphs [OK]

Common Mistakes:

• Using template tags {% %} instead of {{ }} for form rendering
• Calling non-existent render() method
• Confusing as_table with as_p

3. Given this template snippet:

<form method="post">
  {% csrf_token %}
  {{ form.username }}
  {{ form.password }}
  <button type="submit">Login</button>
</form>

What will be displayed for {{ form.username }} and {{ form.password }}?

medium

A. Plain text labels 'username' and 'password' only

B. Input fields for username and password

C. Empty strings because fields are not rendered with as_p

D. Error messages because form is not valid

Solution

1. Step 1: Understand rendering individual form fields

   Rendering {{ form.fieldname }} outputs the HTML input element only for that field, without the label.

2. Step 2: Confirm output for username and password fields

   Each field renders as an input box without its label, so both username and password fields will appear as input fields.

3. Final Answer:

   Input fields for username and password -> Option B

4. Quick Check:

   Individual field rendering = input fields [OK]

Hint: Rendering {{ form.field }} shows input field without label, not just text [OK]

Common Mistakes:

• Thinking {{ form.field }} shows only label text
• Assuming as_p is required for any output
• Confusing empty output with errors

4. You wrote this template code:

<form method="post">
  {{ form.as_p }}
</form>

But when submitting, you get a CSRF verification failed error. What is missing?

medium

A. You should use {{ form.as_table }} instead of as_p

B. You need to add method="get" instead of post

C. You must call form.is_valid() in the template

D. You forgot to include {% csrf_token %} inside the form

Solution

1. Step 1: Identify cause of CSRF verification failure

   Django requires a CSRF token in POST forms to verify requests. Missing {% csrf_token %} causes this error.

2. Step 2: Fix the template by adding CSRF token

   Insert {% csrf_token %} inside the form tags to include the hidden token for security.

3. Final Answer:

   You forgot to include {% csrf_token %} inside the form -> Option D

4. Quick Check:

   CSRF error = missing {% csrf_token %} [OK]

Hint: Always add {% csrf_token %} inside POST forms [OK]

Common Mistakes:

• Changing method to GET instead of adding token
• Trying to validate form in template
• Switching form rendering method without token

5. You want to customize a Django form display by showing each field with a label and input separately in your template. Which code snippet correctly does this?

hard

A. <form method="post">
{% csrf_token %}
<label for="name">Name:</label>
{{ form.name }}
<label for="email">Email:</label>
{{ form.email }}
<button type="submit">Send</button>
</form>

B. <form method="post">
{% csrf_token %}
{{ form.as_p }}
</form>

C. <form method="post">
{% csrf_token %}
{{ form.name.label_tag }}
{{ form.name }}
{{ form.email.label_tag }}
{{ form.email }}
<button type="submit">Send</button>
</form>

D. <form method="post">
{{ form.name.label }}
{{ form.name }}
{{ form.email.label }}
{{ form.email }}
<button type="submit">Send</button>
</form>

Solution

1. Step 1: Understand how to render labels and fields separately

   Django form fields have a label_tag method that outputs the label HTML correctly linked to the input.

2. Step 2: Compare options for correct label rendering

   <form method="post">
     {% csrf_token %}
     {{ form.name.label_tag }}
     {{ form.name }}
     {{ form.email.label_tag }}
     {{ form.email }}
     <button type="submit">Send</button>
   </form>

   uses {{ form.name.label_tag }} and {{ form.name }} which is the proper way to show label and input separately.

   <form method="post">
     {% csrf_token %}
     <label for="name">Name:</label>
     {{ form.name }}
     <label for="email">Email:</label>
     {{ form.email }}
     <button type="submit">Send</button>
   </form>

   uses manual labels which may not link properly.

   <form method="post">
     {{ form.name.label }}
     {{ form.name }}
     {{ form.email.label }}
     {{ form.email }}
     <button type="submit">Send</button>
   </form>

   uses label which is just text, not HTML label tag.

3. Final Answer:

   {{ form.field.label_tag }} {{ form.field }} -> Option C

4. Quick Check:

   Use label_tag for proper label HTML [OK]

Hint: Use {{ field.label_tag }} for correct label HTML [OK]

Common Mistakes:

• Using plain text labels without label_tag
• Forgetting csrf_token in form
• Using label instead of label_tag for labels