Generic editing views¶
The following views are described on this page and provide a foundation for editing content:
django.views.generic.edit.FormViewdjango.views.generic.edit.CreateViewdjango.views.generic.edit.UpdateViewdjango.views.generic.edit.DeleteView
Note
Some of the examples on this page assume that an Article model has been
defined as follows in myapp/models.py:
from django.core.urlresolvers import reverse
from django.db import models
class Author(models.Model):
name = models.CharField(max_length=200)
def get_absolute_url(self):
return reverse('author-detail', kwargs={'pk': self.pk})
FormView¶
-
class
django.views.generic.edit.FormView¶ A view that displays a form. On error, redisplays the form with validation errors; on success, redirects to a new URL.
Ancestors (MRO)
This view inherits methods and attributes from the following views:
django.views.generic.edit.FormViewdjango.views.generic.base.TemplateResponseMixindjango.views.generic.edit.BaseFormViewdjango.views.generic.edit.FormMixindjango.views.generic.edit.ProcessFormViewdjango.views.generic.base.View
Example forms.py:
from django import forms class ContactForm(forms.Form): name = forms.CharField() message = forms.CharField(widget=forms.Textarea) def send_email(self): # send email using the self.cleaned_data dictionary pass
Example views.py:
from myapp.forms import ContactForm from django.views.generic.edit import FormView class ContactView(FormView): template_name = 'contact.html' form_class = ContactForm success_url = '/thanks/' def form_valid(self, form): # This method is called when valid form data has been POSTed. # It should return an HttpResponse. form.send_email() return super(ContactView, self).form_valid(form)
CreateView¶
-
class
django.views.generic.edit.CreateView¶ A view that displays a form for creating an object, redisplaying the form with validation errors (if there are any) and saving the object.
Ancestors (MRO)
This view inherits methods and attributes from the following views:
django.views.generic.edit.CreateViewdjango.views.generic.detail.SingleObjectTemplateResponseMixindjango.views.generic.base.TemplateResponseMixindjango.views.generic.edit.BaseCreateViewdjango.views.generic.edit.ModelFormMixindjango.views.generic.edit.FormMixindjango.views.generic.detail.SingleObjectMixindjango.views.generic.edit.ProcessFormViewdjango.views.generic.base.View
Attributes
-
template_name_suffix¶ The
CreateViewpage displayed to aGETrequest uses atemplate_name_suffixof'_form'. For example, changing this attribute to'_create_form'for a view creating objects for the exampleAuthormodel would cause the defaulttemplate_nameto be'myapp/author_create_form.html'.
Example views.py:
from django.views.generic.edit import CreateView from myapp.models import Author class AuthorCreate(CreateView): model = Author
UpdateView¶
-
class
django.views.generic.edit.UpdateView¶ A view that displays a form for editing an existing object, redisplaying the form with validation errors (if there are any) and saving changes to the object. This uses a form automatically generated from the object’s model class (unless a form class is manually specified).
Ancestors (MRO)
This view inherits methods and attributes from the following views:
django.views.generic.edit.UpdateViewdjango.views.generic.detail.SingleObjectTemplateResponseMixindjango.views.generic.base.TemplateResponseMixindjango.views.generic.edit.BaseUpdateViewdjango.views.generic.edit.ModelFormMixindjango.views.generic.edit.FormMixindjango.views.generic.detail.SingleObjectMixindjango.views.generic.edit.ProcessFormViewdjango.views.generic.base.View
Attributes
-
template_name_suffix¶ The
UpdateViewpage displayed to aGETrequest uses atemplate_name_suffixof'_form'. For example, changing this attribute to'_update_form'for a view updating objects for the exampleAuthormodel would cause the defaulttemplate_nameto be'myapp/author_update_form.html'.
Example views.py:
from django.views.generic.edit import UpdateView from myapp.models import Author class AuthorUpdate(UpdateView): model = Author
DeleteView¶
-
class
django.views.generic.edit.DeleteView¶ A view that displays a confirmation page and deletes an existing object. The given object will only be deleted if the request method is
POST. If this view is fetched viaGET, it will display a confirmation page that should contain a form that POSTs to the same URL.Ancestors (MRO)
This view inherits methods and attributes from the following views:
django.views.generic.edit.DeleteViewdjango.views.generic.detail.SingleObjectTemplateResponseMixindjango.views.generic.base.TemplateResponseMixindjango.views.generic.edit.BaseDeleteViewdjango.views.generic.edit.DeletionMixindjango.views.generic.detail.BaseDetailViewdjango.views.generic.detail.SingleObjectMixindjango.views.generic.base.View
Attributes
-
template_name_suffix¶ The
DeleteViewpage displayed to aGETrequest uses atemplate_name_suffixof'_confirm_delete'. For example, changing this attribute to'_check_delete'for a view deleting objects for the exampleAuthormodel would cause the defaulttemplate_nameto be'myapp/author_check_delete.html'.
Example views.py:
from django.views.generic.edit import DeleteView from django.core.urlresolvers import reverse_lazy from myapp.models import Author class AuthorDelete(DeleteView): model = Author success_url = reverse_lazy('author-list')