This keeps happening to me.... I'll be working on a controller, taking my time and getting it just right. When I hit the save button, I discover my session has timed out and I LOSE THE ENTIRE SET OF CHANGES. There is no way to recover from this and it is annoying as h*ll.
I would recommend we get rid of this session timeout thing altogether, or find a way to save the edits made when it occurs. Or do an "autosave" when the session is about to time out. Editing from a web page is one of the core features of web2py but I'm discovering that it makes our environment FAR less stable and less productive than editing directly with vi or emacs. And this simply should not be the case. Things will seem less catastrophic after I've recovered the hour of edits I just made, but this has happened to me two or three times now and its getting on my nerves. Does this never happen to anyone else? How does it choose to strike me and leave all others alone?? Why am I so lucky?? ;-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
