VisualEditor: Error message texts when the Parsoid service is not around aren't very clear, should be improved
Open, NormalPublic

Description

To reproduce, go to http://www.mediawiki.org/wiki/VisualEditor:Sandbox?veaction=edit , blank the page, save, then you get "Error saving data to server: ..." without too much explaination.


Version: unspecified
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=50475
https://bugzilla.wikimedia.org/show_bug.cgi?id=43147
https://bugzilla.wikimedia.org/show_bug.cgi?id=63149

Details

Reference
bz39057
bzimport raised the priority of this task from to High.
bzimport set Reference to bz39057.
liangent created this task.Aug 5 2012, 9:10 PM

I'm not really sure what else the message should say. If we talk about parsoid, the user will be pretty confused. Are there any suggestions?

Perhaps call it the "editing server"? As in "Sorry, we could not save your changes to the editing server" and "Sorry, we could not get a copy of the page from the editing server" etc.?

Change 157775 had a related patch set uploaded by Jforrester:
Add debugging help to VisualEditor

https://gerrit.wikimedia.org/r/157775

Change 157775 merged by jenkins-bot:
Add debugging help to VisualEditor

https://gerrit.wikimedia.org/r/157775

With the above patch, the former message:

Error loading data from server: parsoidserver-http-bad-status:
500. Would you like to retry?

… turns into:

Error loading data from server: parsoidserver-http-bad-status:
500: Page Fetch failure for "BADURL": Error: getaddrinfo
ENOTFOUND. Would you like to retry?

Which is not ideal, but at least describes things a bit.

greg added a subscriber: greg.Dec 24 2014, 2:57 AM

I just hit this message (was about to reported a semi-dupe) on enwiki. I got the below variant:

Error loading data from server: parsoidserver-http-bad-status:
404: No pages were returned from the API request for $article.
Would you like to retry?" (yes/no)

I hit yes and it worked. So... why not just retry without asking me first?

If it fails again (or for X times, whatever) then give a more generalized "ooops, sorry 'bout that" message with a "click here for more info" dropdown (with the message I just pasted, minus the "would you like to retry?" bit, of course).

Jdforrester-WMF lowered the priority of this task from High to Normal.Jan 15 2015, 12:20 AM
Jdforrester-WMF set Security to None.
Qgil added a subscriber: Qgil.May 27 2015, 6:09 AM

For what is worth, Catalan Viquipedia users confused about an error message from Parsoid:

Alguna cosa no ha funcionat

parsoidserver-http: HTTP 500

Descarta

"Something didn't work" :)

https://ca.wikipedia.org/wiki/Topic:Shssmsofmcgkqhmv

Whatamidoing-WMF added a subscriber: Whatamidoing-WMF.

I agree that "Something went wrong" isn't very helpful. What would be helpful is an explanation of what to do. For example, if it's hopeless and you've just lost all of your work, then acknowledging that it's hopeless would save people the time and stress of trying to save it.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 1 2015, 10:22 PM