Karaage-Cluster/karaage — Issue #50: django 1.2
Author: sorrison
Created: 2012-02-15 22:48:44+00:00
State: open

See:

django 1.2 depreciates some things that were common in 1.1. Not a major problem, but eventually these need to be fixed.

However, it does break some things. The most obvious thing is the new security feature, CSRF Protection. Designed to ensure you can't click on a form submit button on a malicious website that deletes a random user, for example.

Fixing the breakage is easy, in /usr/share/pyshared/andsome/layout/templates/registration/login.html, add "{% csrf_token %}" after the form. Using CSRF to improve security on all forms is also easy.

The problem is this will break on Django 1.1. Django 1.1 has a way of dealing with the same problem, only it is very different.

Does Karaage/placard/etc need to continue supporting Django 1.1?

Brian May