This is another example of Django's reusability. We saw how to create your own form in HTML and render it and get data from it using GET or POST methods. Again, Django does this for you. While it certainly is useful knowing how to do this on a basic level, using Django's Forms API can give you more powerful forms with richer features.
Like models.py, create a file called forms.py in the app where the form is required. Let's create a simple contact form. In forms.py:
forms.py
from django import forms
class SimpleUploadForm (forms.Form):
name = forms.CharField (label = "Enter name")
email = forms.EmailField (label = "Enter email ID", required = False)
dob = forms.DateTimeField (label = "Enter date of birth")
As you can see, just like a model, we created a simple form. Now let's render it from a view.
views.py
from django.shortcuts import render
from forms import SimpleContactForm
def simple_contact_form (request):
form = SimpleContactForm ()
return render (request, "simple_contact_form.html", {"form":form})
Here, we import the SimpleContactForm class from forms.py and initialize its instance in the view. Then we pass that instance as a context to the webpage we're rendering. The view will become clearer when you see the template.
simple_contact_form.html
<html>
<head><title>Simple Contact Form</title></head>
<body>
<form action = "" method = "POST">
<table>
{{ form.as_table }}
</table>
{% csrf_token %}
<input type = "submit" value = "Submit">
</form>
</body>
</html>
Ok now let's break this down. First, form action = "" means the page doesn't change when the button is clicked. Now, in the form, we've passed the SimpleContactForm () instance as form to the template. That will be rendered in the <form> tag. The as_table method displays the form as a table. However, that only contains <tr>, <th> and <td> tags. So we have to add the <table> and </table> tags ourselves. Another form display method is as_p.
The {% csrf_token %} protects POST from, well, CSRF. If you remember I told you to comment that line which included that middleware class. You can uncomment it now and proceed normally.
See you around!
Like models.py, create a file called forms.py in the app where the form is required. Let's create a simple contact form. In forms.py:
forms.py
from django import forms
class SimpleUploadForm (forms.Form):
name = forms.CharField (label = "Enter name")
email = forms.EmailField (label = "Enter email ID", required = False)
dob = forms.DateTimeField (label = "Enter date of birth")
As you can see, just like a model, we created a simple form. Now let's render it from a view.
views.py
from django.shortcuts import render
from forms import SimpleContactForm
def simple_contact_form (request):
form = SimpleContactForm ()
return render (request, "simple_contact_form.html", {"form":form})
Here, we import the SimpleContactForm class from forms.py and initialize its instance in the view. Then we pass that instance as a context to the webpage we're rendering. The view will become clearer when you see the template.
simple_contact_form.html
<html>
<head><title>Simple Contact Form</title></head>
<body>
<form action = "" method = "POST">
<table>
{{ form.as_table }}
</table>
{% csrf_token %}
<input type = "submit" value = "Submit">
</form>
</body>
</html>
Ok now let's break this down. First, form action = "" means the page doesn't change when the button is clicked. Now, in the form, we've passed the SimpleContactForm () instance as form to the template. That will be rendered in the <form> tag. The as_table method displays the form as a table. However, that only contains <tr>, <th> and <td> tags. So we have to add the <table> and </table> tags ourselves. Another form display method is as_p.
The {% csrf_token %} protects POST from, well, CSRF. If you remember I told you to comment that line which included that middleware class. You can uncomment it now and proceed normally.
See you around!
No comments:
Post a Comment