Topic on Project:Support desk

Summary by Wgkderdicke

I extended the session expiry time via $wgObjectCacheSessionExpiry from the default value 3600 (one hour) to 24 * 3600 and this problem here vanished into thin air.

Wgkderdicke (talkcontribs)

I recently updated this wiki here from MW 1.27.17 to 1.31.2. Now I'm experiencing this bug here, too. But it's the Chrome browser instead of the FF/SeaMoneky browser. This is my current Chrome's version: 74.0.3729.169 (Offizieller Build) (64-Bit). The bug rises not every time but then and now and occurs definitely not before the MW update.

I updated Chrome just now. It's version 75.0.3770.90 (Offizieller Build) (64-Bit) now.

AKlapper (WMF) (talkcontribs)
Wgkderdicke (talkcontribs)

It is not any Wikimedia website where I'm experiencing this bug. It is the wiki that I'm running. This wiki was moved to a new server by my provider, then he has changed the PHP version to 7.2 and after that I have updated the MW installation. All this has happend in the last few days. At the moment I'm working on some necessary adjustments. So far, all looks good, even if there is still a little bit work to do. But after the MW update and when I want to save an edited page, then and now this bug occurs in the Chrome browser. From at the end of 2016 I found this here: phabricator.wikimedia.org/T151770. But it's all about Firefox.

AKlapper (WMF) (talkcontribs)
Wgkderdicke (talkcontribs)

After the above-mentioned Chrome update, which I triggered at the same time I wrote this support request, the described bug has not happend again. If it stays that way, there is nothing to report. At the moment I will wait and see.

Wgkderdicke (talkcontribs)

It did not stay that way. It happen not only with the Chrome Browser. It also happend with Firefox and Opera. It happend on my PC with Windows 7 and on another PC with Windows 10.

If one is logged in without the keep me logged in option, one is bluntly logged out, if it happens. If one is logged in with the keep me logged in option, one is faced with the following message after klicking the save button:

Sorry! We could not process your edit due to a loss of session data. Please try again. If it still doesn't work, try logging out and logging back in.

I set $wgExtendedLoginCookieExpiration to null (in MW 1.31 still on 180 * 86400 as default). No effect.

I contacted my provider and asked, if there may be some eager cron job is at work, which kicks sessions off. Nope.

I set $wgExtendedLoginCookieExpiration to null (in MW 1.31 still on 180 * 86400 as default). Nothing.

I set $wgObjectCacheSessionExpiry to 24 * 3600. Bingo! This does the trick! That really annoying and sometimes really frequently shown message as mentioned above has vanished!!!