Changes between Version 25 and Version 26 of NewbieMistakes

Timestamp:

Jul 20, 2006, 8:19:53 PM (18 years ago)

Author:

anonymous

Comment:

--

NewbieMistakes

@@ -247 +247 @@
 }}}
 
-== Reserved name on an application causes import error ==
-
-==== Symptom ====
-
-After creating a new app, with a model that validates, the page request errors out due to existing (and theoretically) available module that can't be loaded.
+== Using reserved name on application breaks admin ==
+
+==== Symptom ====
+
+After creating a new app, with a model that validates, trying to log on to the admin causes an error similar to:
+
+{{{
+ImproperlyConfigured: Error importing middleware django.middleware.common: "No module named ... "
+}}}
 
 ==== Possible cause ====
 
-Check to see that you didn't use a reserved name in naming your application, i.e. "email", "date" and "time" are common application names that would validate when the server starts but will cause an error when requested.  
-
-==== Solution ====
-
-Rename your application using a non-reserved name, i.e., "email_app" instead of "email". Don't forget to do a syncdb to create the newly renamed app in your database. You may also want to go in to your database and drop the old "mis-named" table.
+Check to see that you didn't use a reserved name in naming your application, i.e. "email", "date" and "time" are common application names that would validate when the server starts but will break Django's admin.  
+
+==== Solution ====
+
+Rename your application directory using a non-reserved name, i.e., "email_app" instead of "email". Go into the {{{INSTALLED_APPS}}} section of settings.py and change the name there too. Also, don't forget to do a syncdb to create the newly renamed app in your database. You may also want to go in to your database and drop the old "mis-named" table.