On 3/28/06, Siah <[EMAIL PROTECTED]> wrote: > > Thank you Michael, > > I must add that on my laptop using django's runserver command, this > problem does not exist. > > I am still stock, so all help is greatly appreciated,
Ok, so much for that theory :) Another possibility might be some kind of client side caching going on. There might either be an overly aggressive proxy in between the browser and the site, or the browser might be set to cache pages too much. One way to verify this is to watch the logs as someone browses the site. If they are getting the behaviour you are seeing but you don't see any requests made to the server at the same time then it's probably a browser caching or proxy issue. You should see a request for every page viewed and every item edited, probably with a 200 response code. Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
