Code

Changes between Version 87 and Version 88 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
04/25/07 01:54:28 (7 years ago)
Author:
mtredinnick
Comment:

Added LOGIN_URL change

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v87 v88  
    2121 * April 9, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#RemovedLazyDate Removed `LazyDate`] 
    2222 * April 20, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#MySQLIntrospectionChange MySQL Introspection change] 
    23  
     23 * April 25, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#LOGIN_URLisnowasetting Login URL is now a setting] 
    2424 
    2525== Database constraint names changed == 
     
    116116 
    117117This 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. 
     118 
     119== LOGIN_URL is now a setting == 
     120 
     121In [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 
     122{{{ 
     123#!python 
     124from django.contrib.auth import LOGIN_URL 
     125}}} 
     126 
     127should be changed to refer to `settings.LOGIN_URL` instead.