| | 248 | |
| | 249 | == Reserved name on an application causes import error == |
| | 250 | |
| | 251 | ==== Symptom ==== |
| | 252 | |
| | 253 | 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. |
| | 254 | |
| | 255 | ==== Possible cause ==== |
| | 256 | |
| | 257 | 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. |
| | 258 | |
| | 259 | ==== Solution ==== |
| | 260 | |
| | 261 | 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. |