At a guess, one of your views is returning a string instead of a
HttpResponse object.
This is the wrong forum for this question. This list is for discussing the
development _of_ django, not _with_ django. Your question belongs in
django-users.
On 9 April 2015 at 14:56, wrote:
>
> Error on Dja
Error on Django 1.8:
My site do not use session and cookies, its basic a static site and some
forms.
Django 1.7.7 it's OK.
Traceback (most recent call last):
File
"/usr/local/envs/wscep/lib/python3.4/site-packages/django/core/handlers/wsgi.py",
line 195, in __call__
for c in response
Hi,
Am Thu, 2 Apr 2015 09:15:42 -0700 (PDT)
schrieb Preston Timmons :
> One use case is for validating address forms. We deal with a lot of
> them with varying levels of validation based on country, state, zip
> code, etc. Sometimes, multiple sets of address fields appear on the
> same form. We ca
Since `field_order` will be in Django 1.9 the second clean loop is hardly
needed in my case.
https://github.com/django/django/commit/28986da4ca167ae257abcaf7caea230eca2bcd80
Am 08.04.2015 um 14:20 schrieb Thomas Güttler:
Am 26.03.2015 um 15:12 schrieb Marc Tamlyn:
In particular it is worth n
Am 26.03.2015 um 15:12 schrieb Marc Tamlyn:
In particular it is worth noting the addition of form.add_error[1] in Django
1.7 which makes long clean methods much
nicer to handle.
[1]
https://docs.djangoproject.com/en/1.7/ref/forms/api/#django.forms.Form.add_error
Yes, you are right. My propo
