I see the following as a proper solution: * When the session does expire and end users are presented with a login form, logging in should save the content. This can be done by putting the content etc in hidden input fields for example.
And more suggestions (would be nice to have): 1. Providing a keep alive through ajax, for every 10 keystrokes (monitored through javascript) send a ping to the server which lets it know that your session should be extended by another X minutes. 2. Autosaving - could also test the python code before saving it automatically every X minutes. Similar to the autosave feature in Google docs or so Hope my suggestions are useful :) - sandro On Feb 18, 6:42 pm, Joe Barnhart <joe.barnh...@gmail.com> wrote: > Actually, I found I could _not_ use the back button to recover my > (extensive) edits. As soon as I logged in and pressed tbe back > button, it refreshed the page to the stored version, losing my changes > forever. Then I threw myself on the ground and had a good tantrum. > (Later I found my code changes didn't even work, so there you go.) > > -- Joe B. > > On Feb 18, 9:29 am, annet <jmverm...@planet.nl> wrote: > > > I read the posts above, I had the same problem, but discovered that > > after logging back in I could use the back button of my browser to > > return to the page I wanted to save, and save it. I know this is far > > from an elegant solution, and I haven't tried it on a production > > server, however, it prevented me from lsoing my nerves. > > > I hope a better solution comes up soon. > > > Annet --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
