Update on this issue, things seemed to work themselves out when I commented out the python eggs line in each of the virtual hosts settings and re-enabled the virtual hosts using the a2ensite in apache...
I hope that this might be a help to any other web dev newbies out there :) Thanks to everyone who posted ideas on this thread! On Oct 17, 6:27 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Oct 17, 5:38 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > > On 17-Oct-07, at 7:31 AM, Wiley wrote: > > > > Kenneth and Bob, the PythonInterpreter thing was the first thing I > > > checked (because it was in the official docs) if you notice I have > > > different PythonInterpreters already set in the two virtual hosts in > > > my original post...am I missing something obvious? > > > how about the secret key in settings.py? Browser cache? I have been > > bitten by browser cache with two nearly identical sites. > > Just a thought, not knowing how Django works, but how is the cache > backend used by Django? If the cache backend is memcached, do > different sites on the same machine isolate data in the memcache > instance sufficiently that they cannot interfere with each other? > Would having some key setting in the settings.py the same for > different sites allow sharing of stuff that shouldn't be shared? > > Graham --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
