I will try to put something together. I have a fairly detailed trace that I have put in the session code that shows my session variables are set when it calls one of my views, but the trace shows that the next session save only a new session variable set in that view exists all the other session variables have disappeared. I am not knowingly clearing the other variables. Thanks for your interest. John
On Jan 8, 10:34 am, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > On Thu, 2009-01-08 at 02:30 -0800, bradders wrote: > > Can anyone recommend a session system that works more reliably than > > the built-in Django session handling? I am finding that after calling > > 2 or 3 different views the session variables that were stored at login > > time get cleared. I am using django 1.0, but I think the problem > > existed in earlier versions. > > Perhaps if you could provide a replicable test case we could look at > whatever problem may exist in the Django system. To the best of my > knowledge it doesn't just arbitrarily throw away variables, but there's > not way to tell what you're doing from the description you've provided. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
