This wiki config option seems relevant:
https://www.mediawiki.org/wiki/Manual:$wgObjectCacheSessionExpiry
We don't set this right now, and it defaults to 1 hour.
--
For information about J forums see
Yeah, me too. I tried earlier today to create a loss of data by using
two browsers, but I couldn't.
Henry Rich
On 5/11/2022 3:42 PM, Devon McCormick wrote:
I usually do the first two steps Ian mentions - save all in the clipboard
and try again. Lately I've gotten even lazier and just try
I usually do the first two steps Ian mentions - save all in the clipboard
and try again. Lately I've gotten even lazier and just try again right
away and it hasn't failed in at least 10 tries.
On Wed, May 11, 2022 at 2:23 PM Ian Clark wrote:
> Recent Changes…
> Thanks, Raul. That's a start.
Recent Changes…
Thanks, Raul. That's a start. I'll give it a try next time it happens.
Trouble is, it's not a condition that can be triggered at will. At least, I
don't know how.
MediaWiki does a lot of logging, in so many different ways. When I have a
spare week I must study it more.
On Wed, 11
The Recent Changes link on the left side of wiki pages is useful for
checking recent (potential) edits.
I know, I know, this sounds "obvious" but with so many competing
pieces of potentially useful information in front of us, "obvious" is
all-too-often in short supply.
I hope this helps,
--
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
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).
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
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
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
10 matches
Mail list logo
