Page MenuHomePhabricator

Problems to save changes in eu.wikipedia
Closed, DuplicatePublic


Since yesterday we're experiencing problems to save new articles or changes in existing articles. The error message is in basque, so I don't know the exact code, but it says that "the change could not be processed due to data-loss in the session. Please, try again. If the problem continues, please log-out and log-in again".

Neither of those solution is working.

Event Timeline

Theklan created this task.Dec 11 2016, 9:36 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 11 2016, 9:36 AM
Framawiki added a subscriber: Framawiki.EditedDec 11 2016, 10:15 AM

Hello, have you a link to discussion about this on the wiki ? Can you give example of concerned pages ?

We don't even have a discussion on it, as it's difficult to make changes. We have been discussing it with others via Whatsapp and yes, many people is experiencing this issue. You can try changing an article, for example I have this problem now with

Theklan added a comment.EditedDec 11 2016, 1:29 PM

It saved after 10 attempts.
But the problem is still there. You can try making any change to any article (as far is I tried, also for categories).

@Anomie @Tgr Could you please dig in Logstash if this is something related to AuthManager / CentralAuth ? Thanks.

Restricted Application added a subscriber: Matanya. · View Herald TranscriptDec 11 2016, 3:13 PM
MarcoAurelio renamed this task from Problems to save changes in eu:wp to Problems to save changes in eu.wikipedia.Dec 11 2016, 3:48 PM

mw.Api error: http Object { xhr: Object, textStatus: "error", exception: "" } load.php:13281:4

is what I get after opening the web browser's developer tools and their 'console' tab (for more information please see: Firefox ≥24; Internet Explorer; Google Chrome; Apple Safari; Opera) and going to a random page like (note the &debug=true), then adding a line in the wiki text editor, and pressing ""Erakutsi aurreikuspena"" (Show preview).

(On a completely unrelated note: All gadgets are broken as they have not been ported to ResourceLoader.)

Aklapper triaged this task as High priority.Dec 11 2016, 4:44 PM
Restricted Application added a subscriber: Dereckson. · View Herald TranscriptDec 11 2016, 4:44 PM

Can't repro on Chrome 56 or Firefox 52 (but I can confirm issues with gadgets).

Same, I haven't this message error in FF.

@Krinkle is good with updating Gadgets. If he's avalaible he might be able to have a look at them (and delete duplicate messages in the meanwhile).

Tgr added a comment.Dec 11 2016, 8:30 PM

@Anomie @Tgr Could you please dig in Logstash if this is something related to AuthManager / CentralAuth ? Thanks.

It's hard to find useful log records without details like a page name and an approximate timestamp (unless you have a good idea what kind of log event you are looking for, and AuthManager / CentralAuth is unlikely to be it). I checked the one page mentioned above but there are no interesting logs.

Right now (from 00:05 to 00:15, trying to save new article [])... just impossible.

After logging out, I could save the article as an anonymous IP. But after logging in again, the problem continues.

Could you try disabling all gadgets?

Tgr added a comment.Dec 12 2016, 2:56 AM

@Theklan if you can reproduce, could you upload in a private paste the exact request network details? (On Chrome or Firefox, press F12 to bring up the Developer Toolbar, then select Network tab, then reproduce the issue, then right-click in the middle area and select "Save as HAR". You should probably log out afterwards as the HAR file contains session identifiers.)

Tgr added a comment.Dec 12 2016, 8:45 AM

Got it, thanks! I asked an admin to delete it since it contains private data and was uploaded as public (I can send it to anyone else who wants to do some debugging). I'll look into it tomorrow.

Tgr added a comment.Jan 6 2017, 12:06 AM

Apologies for taking so long to look at this. It's the same issue as T151770: a cross-domain request is made to some gadget, that results in a bunch of new cookies being set, and the browser (FF50 like in the other cases) forgets the local session cookie.