The following views are described on this page and provide a foundation for\nediting content:
\nFormViewLink to this heading#A view that displays a form. On error, redisplays the form with validation\nerrors; on success, redirects to a new URL.
\nAncestors (MRO)
\nThis view inherits methods and attributes from the following views:
\nExample myapp/forms.py:
\nfrom django import forms\n\nclass ContactForm(forms.Form):\n name = forms.CharField()\n message = forms.CharField(widget=forms.Textarea)\n\n def send_email(self):\n # send email using the self.cleaned_data dictionary\n pass\nExample myapp/views.py:
\nfrom myapp.forms import ContactForm\nfrom django.views.generic.edit import FormView\n\nclass ContactFormView(FormView):\n template_name = 'contact.html'\n form_class = ContactForm\n success_url = '/thanks/'\n\n def form_valid(self, form):\n # This method is called when valid form data has been POSTed.\n # It should return an HttpResponse.\n form.send_email()\n return super().form_valid(form)\nExample myapp/contact.html:
\n<form method="post">{% csrf_token %}\n {{ form.as_p }}\n <input type="submit" value="Send message">\n</form>\nA base view for displaying a form. It is not intended to be used directly,\nbut rather as a parent class of the\ndjango.views.generic.edit.FormView or other views displaying a\nform.
Ancestors (MRO)
\nThis view inherits methods and attributes from the following views:
\n\nCreateViewLink to this heading#A view that displays a form for creating an object, redisplaying the form\nwith validation errors (if there are any) and saving the object.
\nAncestors (MRO)
\nThis view inherits methods and attributes from the following views:
\ndjango.views.generic.detail.SingleObjectTemplateResponseMixin
Attributes
\nThe CreateView page displayed to a GET request uses a\ntemplate_name_suffix of '_form'. For\nexample, changing this attribute to '_create_form' for a view\ncreating objects for the example Author model would cause the\ndefault template_name to be 'myapp/author_create_form.html'.
When using CreateView you have access to self.object, which is\nthe object being created. If the object hasn’t been created yet, the\nvalue will be None.
Example myapp/views.py:
\nfrom django.views.generic.edit import CreateView\nfrom myapp.models import Author\n\nclass AuthorCreateView(CreateView):\n model = Author\n fields = ['name']\nExample myapp/author_form.html:
\n<form method="post">{% csrf_token %}\n {{ form.as_p }}\n <input type="submit" value="Save">\n</form>\nA base view for creating a new object instance. It is not intended to be\nused directly, but rather as a parent class of the\ndjango.views.generic.edit.CreateView.
Ancestors (MRO)
\nThis view inherits methods and attributes from the following views:
\n\nMethods
\nSets the current object instance (self.object) to None.
Sets the current object instance (self.object) to None.
UpdateViewLink to this heading#A view that displays a form for editing an existing object, redisplaying\nthe form with validation errors (if there are any) and saving changes to\nthe object. This uses a form automatically generated from the object’s\nmodel class (unless a form class is manually specified).
\nAncestors (MRO)
\nThis view inherits methods and attributes from the following views:
\ndjango.views.generic.detail.SingleObjectTemplateResponseMixin
Attributes
\nThe UpdateView page displayed to a GET request uses a\ntemplate_name_suffix of '_form'. For\nexample, changing this attribute to '_update_form' for a view\nupdating objects for the example Author model would cause the\ndefault template_name to be 'myapp/author_update_form.html'.
When using UpdateView you have access to self.object, which is\nthe object being updated.
Example myapp/views.py:
\nfrom django.views.generic.edit import UpdateView\nfrom myapp.models import Author\n\nclass AuthorUpdateView(UpdateView):\n model = Author\n fields = ['name']\n template_name_suffix = '_update_form'\nExample myapp/author_update_form.html:
\n<form method="post">{% csrf_token %}\n {{ form.as_p }}\n <input type="submit" value="Update">\n</form>\nA base view for updating an existing object instance. It is not intended to\nbe used directly, but rather as a parent class of the\ndjango.views.generic.edit.UpdateView.
Ancestors (MRO)
\nThis view inherits methods and attributes from the following views:
\n\nMethods
\nSets the current object instance (self.object).
Sets the current object instance (self.object).
DeleteViewLink to this heading#A view that displays a confirmation page and deletes an existing object.\nThe given object will only be deleted if the request method is POST. If\nthis view is fetched via GET, it will display a confirmation page that\nshould contain a form that POSTs to the same URL.
Ancestors (MRO)
\nThis view inherits methods and attributes from the following views:
\ndjango.views.generic.detail.SingleObjectTemplateResponseMixin
Attributes
\nThe DeleteView page displayed to a GET request uses a\ntemplate_name_suffix of '_confirm_delete'. For\nexample, changing this attribute to '_check_delete' for a view\ndeleting objects for the example Author model would cause the\ndefault template_name to be 'myapp/author_check_delete.html'.
Example myapp/views.py:
\nfrom django.urls import reverse_lazy\nfrom django.views.generic.edit import DeleteView\nfrom myapp.models import Author\n\nclass AuthorDeleteView(DeleteView):\n model = Author\n success_url = reverse_lazy('author-list')\nExample myapp/author_confirm_delete.html:
\n<form method="post">{% csrf_token %}\n <p>Are you sure you want to delete "{{ object }}"?</p>\n <input type="submit" value="Confirm">\n</form>\nA base view for deleting an object instance. It is not intended to be used\ndirectly, but rather as a parent class of the\ndjango.views.generic.edit.DeleteView.
Ancestors (MRO)
\nThis view inherits methods and attributes from the following views:
\n\n