Changes between Version 16 and Version 17 of BackwardsIncompatibleChanges

Timestamp:

Oct 19, 2005, 1:40:11 AM (19 years ago)

Author:

eugene@…

Comment:

minor typo correction, more info on current behavior of 404 and 500 templates, notes on directory rewrites

BackwardsIncompatibleChanges

@@ -137 +137 @@
    * Add {{{"django.middleware.sessions.SessionMiddleware"}}} to {{{MIDDLEWARE_CLASSES}}}, if it's not already in there.
    * If you've created any custom admin templates, add the appropriate line from the admin {{{TEMPLATE_DIRS}}} setting to your "main" {{{TEMPLATE_DIRS}}}.
+     * '''Current behavior:''' Django looks up 404/500 templates in your {{{TEMPLATE_DIRS}}} without any fallback mechanism. Make sure you have these templates available.
    * If you've created any custom admin templates, note that the template inheritance structure has changed. All admin templates are now within an {{{admin}}} subdirectory of the template directory. The following admin templates are directly affected by this change:
-     * 400 --> admin/404
+     * 404 --> admin/404
      * 500 --> admin/500
      * base --> admin/base
@@ -165 +166 @@
    Change that {{{"admin"}}} to whatever URL you were using for the admin site.
 
+If you use external mapping to files and directories (e.g., using mod_rewrite), do the following:
+
+ * Make sure you don't redirect {{{/admin}}} to another instance of Django with different settings (e.g., using admin.py). Now '''one''' instance of Django handles admin '''and''' your main site. Do not redirect now!
+ * If you had a mapping of admin media files, make sure that it points to new directory, which is {{{/your/path/to/django/contrib/admin/media}}}.
+
 The following steps are optional but will tighten your code up. All assume your project is called {{{myproject}}}.