Strange. ANyway, I would just increate the timeout time so that the problem does not arise again.
Massimo On Oct 23, 12:38 pm, Joe Barnhart <[EMAIL PROTECTED]> wrote: > Actually, this did not work for me in FireFox 3. As soon as I used > the back key, the edit control refreshed itself and lost all of my > edits. There was no way to recover my edits from the browser at all. > I am surprised that you say it works for you. > > As for editing files instead of using the web interface -- I thought > the web interface was one of the "advantages" of web2py over similar > offerings. It's harder to use files on web2py because our interface > is not set up to easily allow file editing remotely. We rely on other > means such as ssh and ftp to edit files remotely, which reduces the > convenience of web2py somewhat when used in that mode. > > -- Joe > > On Oct 23, 6:59 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > And you can always use the browser to go [back] and retrieve work at > > any previous stage (works for me with firefox). > > > Massimo > > > On Oct 23, 8:58 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > > I know but once you are aware of this problem it is gone because you > > > have the options to: > > > 1) edit the admin/models/0.py file and increase the expiration time > > > 2) you can edit the files without the web based interface using any > > > other editor you like > > > > Massimo > > > > On Oct 23, 4:59 am, "Phyo Arkar" <[EMAIL PROTECTED]> wrote: > > > > > It wont be hard to make ajax saves . > > > > > On Thu, Oct 23, 2008 at 9:37 AM, achipa <[EMAIL PROTECTED]> wrote: > > > > > > The real question here is what web2py can/could do about people > > > > > landing on unexpected pages, which then go to login. A form submission > > > > > on a web2py restart, loss of cookie, browser restart, session timeout, > > > > > etc could, in theory, be preserved (the login page should redirect/ > > > > > resubmit to the original page). Lost edits are just a special case of > > > > > this. > > > > > > In this specific case, again, as an idea, the editor actually could do > > > > > server assisted autosaves: just save the document in a temp admin > > > > > table or file, probably through some AJAX magic to make it transparent > > > > > to the user. In either case, it would be a serious mod to both web2py > > > > > and the editor itself, which is just a borrowed component in web2py. > > > > > > On Oct 23, 9:00 am, Keith Edmunds <[EMAIL PROTECTED]> wrote: > > > > > > On Wed, 22 Oct 2008 23:12:24 -0700 (PDT), [EMAIL PROTECTED] said: > > > > > > > > This is one reason > > > > > > > why many people don't trust web editors -- they are too prone to > > > > > > > lose > > > > > > > work. > > > > > > > Whilst I agree with the basic point you make about somehow saving > > > > > > the > > > > > > context of the editing if possible, if you don't trust web editors > > > > > > then > > > > > > why are you using one?? None of my web2py editing is done via the > > > > > > web > > > > > > interface for a number of reasons, not least of which is that there > > > > > > is no > > > > > > recovery journal. > > > > > > > Keith --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
