Changes between Initial Version and Version 1 of Ticket #14143


Ignore:
Timestamp:
Aug 20, 2010, 7:10:32 AM (14 years ago)
Author:
Karen Tracey
Comment:

Fixed formatting, please use WikiFormatting and preview before submitting. Also this problem is almost certainly a configuration problem on your machine, so would better be direction to the django-users mailing list or #django irc channel.

Both of the errors you mention would happen if your PYTHONPATH was pointing to a pre-1.2 Django: your 1.2 style database definitions would not be recognized and the new 1.2 messages module would not be found. So I suspect somehow your environment has been changed and you are no longer picking up the right version of Django for your project.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14143

    • Property Resolutioninvalid
    • Property Status newclosed
  • Ticket #14143 – Description

    initial v1  
    55Basically I started a new project, configured everything and linked it to my database, sync-ed everything and got the admin working fine. Wrote a new blog app worked out the kinks by importing it in the manage.py shell until it all worked fine and added it to my installed apps and went to sync but get:
    66
     7{{{
     8
    79django.core.exceptions.ImproperlyConfigured?: You haven't set the DATABASE_ENGINE setting yet.
     10
     11}}}
    812
    913Now I know what this means normally, but as I said I had previously synced the admin and got everything working, all that I had changed was adding the model to my installed apps.
     
    1115Here is the exert from my settings.py:
    1216
     17
     18{{{
    1319DATABASES = {
    1420
     
    1925......
    2026
     27}}}
    2128About the same time manage.py shell throws up no module named messages. Checked and for some reason django.contrib.messages is no longer on the python path. Added it location to .pth file in the dist-packages, but still it cant find it. I had a similar problem importing contrib.page module and had to re-install everything but it finds pages fine now.
    2229
Back to Top