On 28 Lug, 15:33, Maksymus007 <maksymus...@gmail.com> wrote:
> The same all the sentences link '1.1 and 1.2 are compatible'.
> They are not.
You are right: that page doesn't mention csrf changes.
I upgraded few installations from 1.0 and from 1.1 to 1.2
and the only undocumented change I remember is exactly the csrf.
I just added {% csrf_token %} after form tag in every template.
as you can read in
http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#how-to-use-it
> I have quite big application written in 1.1 - still can't fully run it on 1.2.
> As I discovered: forms fields set to be blank=True and null=True when
> left blank on 1.1 get null value as expected, on 1.2 the get empty
> string - which crashes if database has constraints.
Sorry but I didn't encounter this problem.
Besides the csrf, all my upgrades went smoothly.
Regards
Massimiliano
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
