Changes between Version 87 and Version 88 of BackwardsIncompatibleChanges

Timestamp:

Apr 25, 2007, 3:54:28 AM (18 years ago)

Author:

Malcolm Tredinnick

Comment:

Added LOGIN_URL change

BackwardsIncompatibleChanges

@@ -21 +21 @@
  * April 9, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RemovedLazyDate Removed `LazyDate`]
  * April 20, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#MySQLIntrospectionChange MySQL Introspection change]
-
+ * April 25, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#LOGIN_URLisnowasetting Login URL is now a setting]
 
 == Database constraint names changed ==
@@ -116 +116 @@
 
 This will only be apparent if you introspect a database table using 0.96 and again using [5042] or later: you will have slightly different Django models generated if there are any `CHAR(n)` columns. However, no real code changes should be necessary.
+
+== LOGIN_URL is now a setting ==
+
+In [5072], we moved the LOGIN_URL constant from django.contrib.auth into the settings module. This was part of a broader change to make these URLs (including logout and post-login redirect) configurable. Code that previously read
+{{{
+#!python
+from django.contrib.auth import LOGIN_URL
+}}}
+
+should be changed to refer to `settings.LOGIN_URL` instead.