ok, i am planning to remove all traces of all django installations from my system, and re-install the dev version (and if that still does not work 3.1) under virtualenv.
Will repost here if I still see problems. Nara On Sep 10, 7:16 pm, Babatunde Akinyanmi <tundeba...@gmail.com> wrote: > Hi nara, > Please post the debug output you get when you try to view the admin > page from your browser. > > Meanwhile, while switching versions of django, you have to make sure > you remove completely every file from the old version. Failure to do > that will break django. > > On 9/10/11, nara <nar...@gmail.com> wrote: > > > > > > > > > > > ok, I switched to the 1.3.1 released version of Django, and > > also tried Python2.6 instead of Python2.7 on the dev version > > of Django. Things are still majorly broken, see the following > > in the django shell on a fresh startproject, I could not > > import even the top level django module. Then, > > I set PYTHONPATH to /home/nara/Django1.3/django, > > and after that, in the shell, I am still unable to > > directly import the admin module, I have to do this: > > >>>> import django > >>>> import django.contrib > >>>> import django.contrib.admin > > > So, the problem is not just in the admin module, it > > is likely all over the place (entire django module hierarchy). > > > Oh well, looks like I have to cool this off for a while. > > > Thanks for everyone's help. > > Nara > > > On Sep 10, 2:17 pm, nara <nar...@gmail.com> wrote: > >> I'll get through this yet :) > > >> I tried the commands you have under the django shell, and I got > >> 'example.com' > >> on the django.Site query, and not an error. Also, interestingly, > >> within the shell, I don't see > >> django on the sys.path at all (shown below), but I do see my project > >> mblog. This could > >> be the cause of not seeing the admin. I could switch to python 2.6 > >> instead > >> of python 2.7, but I doubt that that is going fix this issue. Dropping > >> my project > >> table and doing a new syncdb did not help either. > > >> Here is the path, prettified: > > >> ['/home/nara/dj/mblog' > >> '/usr/local/lib/python2.7/dist-packages/setuptools-0.6c11-py2.7.egg' > >> '/usr/local/lib/python2.7/dist-packages/grin-1.2.1-py2.7.egg' > >> '/usr/local/lib/python2.7/dist-packages/pip-1.0.2-py2.7.egg' > >> '/usr/lib/python2.7' > >> '/usr/lib/python2.7/plat-linux2' > >> '/usr/lib/python2.7/lib-tk' > >> '/usr/lib/python2.7/lib-old' > >> '/usr/lib/python2.7/lib-dynload' > >> '/usr/local/lib/python2.7/dist-packages' > >> '/usr/lib/python2.7/dist-packages' > >> '/usr/lib/python2.7/dist-packages/PIL' > >> '/usr/lib/pymodules/python2.7/gtk-2.0' > >> '/usr/lib/python2.7/dist-packages/gst-0.10' > >> '/usr/lib/python2.7/dist-packages/gtk-2.0' > >> '/usr/lib/pymodules/python2.7' > >> '/usr/lib/pymodules/python2.7/ubuntuone-control-panel' > >> '/usr/lib/pymodules/python2.7/libubuntuone' > >> '/usr/lib/pymodules/python2.7/ubuntuone-storage-protocol' > >> '/usr/lib/pymodules/python2.7/ubuntuone-client'] > > >> Thanks > >> Nara > > >> On Sep 9, 9:56 pm, Babatunde Akinyanmi <tundeba...@gmail.com> wrote: > > >> > Hi nara, > >> > This error is normally thrown when the sites app is being used in a > >> > django project. I think it can also occur if the sites tables in the > >> > database is not properly created during django-admin startproject. > >> > Someone else reported that he was able to solve the problem by using a > >> > user name without special characters. > > >> > This might be difficult to debug since you are using a development > >> > version however: > >> > 1. Go to the inbuilt django shell and enter these commands: > >> > from django.contrib.sites.models import Site > >> > From django.conf import settings > >> > x = settings.SITE_ID > >> > Site.objects.get(pk=x) > > >> > You should get the same "site matching query does not exist" error. > >> > Now print x and then check the django_site_table in your database. x > >> > should be the same as the primary key of what you have in the table. > >> > If it isn't, drop the table and syncdb again. > > >> > On 9/10/11, nara <nar...@gmail.com> wrote: > > >> > > yes, admin is in INSTALLED_APPS. BTW, the basic site works fine if I > >> > > turn > >> > > off all admin. admin is not strictly necessary, it is just a nicety. > > >> > > One strange thing though: I have had to set PYTHONPATH and > >> > > explicitly set it to ~/mblog:~/mblog/apps:~/mblog/apps/myblog, > >> > > even though __init__.py files exist at all levels! Could > >> > > something as basic as Python module search be broken? > >> > > I am using latest Python 2.7 on Ubuntu 11.04 > > >> > > Thanks > >> > > Nara > > >> > > On Sep 9, 5:35 pm, Casey Greene <csgre...@princeton.edu> wrote: > >> > >> Is admin in INSTALLED_APPS? > > >> > >>https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-INSTA... > > >> > >> Casey > > >> > >> On 09/09/2011 07:04 PM, nara wrote: > > >> > >> > Hi, > > >> > >> > I am a newbie, and I am trying a very basic blog site to get > >> > >> > familiar > >> > >> > with the latest development release. I followed the directions in > >> > >> > the > >> > >> > tutorial (part 2) to try and get the automatic admin going. > >> > >> > However, > >> > >> > here is what I get on the url localhost:8000/admin/ > > >> > >> > DoesNotExist at /admin/ > > >> > >> > Site matching query does not exist. > > >> > >> > Request Method: GET > >> > >> > Request URL: http://localhost:8000/admin/ > >> > >> > Django Version: 1.4 pre-alpha SVN-16741 > >> > >> > Exception Type: DoesNotExist > >> > >> > Exception Value: > > >> > >> > Site matching query does not exist. > > >> > >> > Further, syncdb, even on a brand new database, does not create > >> > >> > tables > >> > >> > for the admin, just for django and my blog model. > > >> > >> > Ideas, suggestions? > > >> > >> > Thanks > >> > >> > Nara > > >> > > -- > >> > > You received this message because you are subscribed to the Google > >> > > Groups > >> > > "Django users" group. > >> > > To post to this group, send email to django-users@googlegroups.com. > >> > > To unsubscribe from this group, send email to > >> > > django-users+unsubscr...@googlegroups.com. > >> > > For more options, visit this group at > >> > >http://groups.google.com/group/django-users?hl=en. > > >> > -- > >> > Sent from my mobile device > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-users@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. > > -- > Sent from my mobile device -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
