OK, I'm having a silly problem: In one view I set a property in the user's session. Then, in the template returned by the same view, a custom template tag queries the database Session objects and displays a message depending on the property set before.
However, this doesn't work the first time. Only after the second time does the template tag "get" the modified session. I would like the processing to happen in the following order: request -> my view modifies session -> session is saved in the db -> my template tag reads sessions -> render response However, I imagine that the order is like this: request -> my view modifies session -> my template tag reads sessions -> render response -> session is saved in the db And this is why it works the second time round. Is there any way I can call save() on the session explicitly ? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
