I too would like a clear statement of best practice for recovering from this situation. Maybe as a flowchart.
Whenever I see the warning message (usually after hitting "Save changes") my reflex action is to do what Bob recommends: scroll to the "editing area" and copy/paste it for emergency recovery. But it's so rarely necessary. Usually it works to simply hit the "Save Changes" button a second time. (If I dare.) On occasions when I've panicked (and thus forgotten how exactly I responded) it's subsequently emerged that the server has actually registered my changes and updated the page. But to verify this fact is not a simple task. If someone could only tell me how best to do it – as a reflex action – the "demon warning" would no longer be an issue for me. Good task-support for the task of recovery might include -- a button which reliably copies the editing area to the system pasteboard, not disruptable by a sick server or connection, -- a confirmation message fom the server that the last "Save Changes" button-click did not (logically) alter the page contents. Ian On Wed, 11 May 2022 at 16:51, Henry Rich <[email protected]> wrote: > I think it's simply a loss of your reservation after a timeout. > Wikipedia does the same. > > When you start editing a page, you get rights to it for a short time > (maybe 5 min?). After that, it's up for grabs. When you repeat your > save, it goes through (parhaps after a check for conflict). > > Henry Rich > > On 5/11/2022 11:41 AM, 'robert therriault' via General wrote: > > Before reloading the page, I would suggest copying your most recent > edits if you can. > > > > Then if you lose the edits on reloading, you should be able go to the > original page, edit and paste in your saved edits to continue on. > > > > I have seen this as well, although not very often and I put it down to > an interruption to my internet that might not be noticed by me on my > browser, > > but was enough to disrupt the editing process within the wiki. > > > > Cheers, bob > > > >> On May 11, 2022, at 08:33, Raul Miller <[email protected]> wrote: > >> > >> I suspect that that message means that your browser has lost track of > >> a cookie or failed to perform a secondary request. > >> > >> It does not seem to be a timeout. Or, if that message does represent a > >> timeout, there are also other issues which can trigger the problem: > >> Sometimes simply reloading the page has been sufficient to make the > >> message go away. > >> > >> I hope this helps, > >> > >> -- > >> Raul > >> > >> On Tue, May 10, 2022 at 11:29 PM Arthur Anger <[email protected]> > wrote: > >>> Now and then, after many minutes of making editing changes to a Wiki > page, a Save request is greeted by: > >>> Sorry! We could not process your edit due to a loss of session data. > >>> > >>> You might have been logged out. . . . > >>> > >>> Is this a timeout in the editor, and can it be lengthened? > >>> > >>> Is this instead a result of temporary loss of communication, which > does occur occasionally, but doesn't often have a visual effect during an > editing session? > >>> > >>> I have sometimes managed to copy the edited page and reinstate it > later, but wonder if there is standard recovery procedure. > >>> > >>> Thanks. > >>> --Art > >>> ---------------------------------------------------------------------- > >>> For information about J forums see http://www.jsoftware.com/forums.htm > >> ---------------------------------------------------------------------- > >> For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > -- > This email has been checked for viruses by AVG. > https://www.avg.com > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
