Hey! A full traceback could be helpful.
A lot of time when you've got really strange import errors they have something to do with circular imports. Did you change any imports right before or after the upgrade? Regards, Friðrik Már On Jul 9, 2009, at 3:25 PM, huw_at1 wrote: > > Hi all, > > I have just been moving my website to a production server and am > having some difficulty getting it working. I have upgraded the Django > from 1.0 on my development server to 1.1 on the production server. > When I try to access the admin pages I get an Internal Server Error > and a message in the apache logs stating "Import Error: No module > named urls". I have tried running the shell and importing the urls > module from within and outside of the local directory both of which > work fine. > > I'm guessing it's either some value in my settings file or something > is non-backwards compatible going from 1.0 to 1.1 but I am a bit > clueless as to what atm. Any suggestions would be most welcome. > > Many thanks > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
