[Django] #25973: Django 1.9 CBV - Form field error still being rendered in template after deletion

6 views
Skip to first unread message

Django

unread,
Dec 23, 2015, 4:51:38 AM12/23/15
to django-...@googlegroups.com
#25973: Django 1.9 CBV - Form field error still being rendered in template after
deletion
-------------------------------+---------------------------------
Reporter: pshumba | Owner: nobody
Type: Bug | Status: new
Component: Generic views | Version: 1.9
Severity: Normal | Keywords: Form error deletion
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+---------------------------------
Before rendering template code is supposed to remove email field error on
unique validation
"Foo with this Email address already exists."

Code works on previous version of Django 1.8.4
Django 1.9 displays error in template

Model:
{{{
class Foo(models.Model):
email = models.EmailAddress(unique = True)
}}}

View:
{{{
from django.views.generic import CreateView

Class BarCreateView(CreateView):

def form_invalid(self, form):
if form.has_error('email', 'unique'):
form.errors.pop('email', None)
return super(BarCreateView, self).form_invalid(form)
}}}

Template:
{{{
<form id="login_form" method="post" action="">
{% csrf_token %}
{{form}}
<input type="submit" value="Submit" />
</form>
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/25973>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Dec 23, 2015, 5:06:16 AM12/23/15
to django-...@googlegroups.com
#25973: Django 1.9 CBV - Form field error still being rendered in template after
deletion
-------------------------------------+-------------------------------------
Reporter: pshumba | Owner: nobody
Type: Bug | Status: closed

Component: Generic views | Version: 1.9
Severity: Normal | Resolution: duplicate

Keywords: Form error deletion | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by alasdairnicol):

* status: new => closed
* needs_better_patch: => 0
* resolution: => duplicate
* needs_tests: => 0
* needs_docs: => 0


Comment:

I believe this is a duplicate of #25548, which will be fixed in the
upcoming 1.9.1 release. Please could you test with the latest 1.9.X
branch?

--
Ticket URL: <https://code.djangoproject.com/ticket/25973#comment:1>

Reply all
Reply to author
Forward
0 new messages