Last modified: 2014-08-09 00:05:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T50773, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48773 - When saving failed user has no way to retry and even if many failed YOU ARE NOT NOTIFIED
When saving failed user has no way to retry and even if many failed YOU ARE N...
Status: RESOLVED DUPLICATE of bug 69314
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: Unprioritized normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-24 11:54 UTC by Rainer Rillke @commons.wikimedia
Modified: 2014-08-09 00:05 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Rainer Rillke @commons.wikimedia 2013-05-24 11:54:07 UTC
Original bug title:
When saving failed user has no way to retry and even if many failed YOU ARE NOT NOTIFIED

I just translated 
https://commons.wikimedia.org/w/index.php?title=Special:Translate&group=page-Commons%3AWikim%C3%A9dia+France&filter=&action=translate

and somehow my login was lost and "the modification was aborted by an extension hook". I was unable to get it saved and had to open a separate tab and paste each single translation I intended to contribute to Commons.

What makes this that even more worse is this automated scroll down that happens after you saved a translation unit. This way you aren't aware of the issue.
Comment 1 Andre Klapper 2013-05-24 14:13:55 UTC
Developers should probably investigate why that logout happened and in which cases "the modification was aborted by an extension hook" could be triggered (plus what that generic message means).
Comment 2 Andre Klapper 2013-05-24 14:14:41 UTC
(In reply to comment #0)
> and somehow my login was lost

Getting a warning about it is covered in bug 48775; thanks for filing that.
Comment 3 Rainer Rillke @commons.wikimedia 2013-05-24 15:02:34 UTC
Yes, this is about a retry button or an automated retry mechanism.

The extension hook was abuse filter which prevented new page creation for anon users. And yes, the error message could be improved but this is the one, the API returns.
Comment 4 Purodha Blissenbach 2013-05-31 12:37:00 UTC
Just FYI, when saving fails due to other errors, such as a timeout or a lost internet connection, you are not notified as well. 
The "Saving..." notification is shown virtually forever.
Re-editing the message unlocks the save button, but clicking it seems to have no effect.
We lack a (manual) retry mechanism. Maybe that should go to a separate bug?
Comment 5 Nemo 2013-09-09 06:01:56 UTC
(In reply to comment #4)
> Just FYI, when saving fails due to other errors, such as a timeout or a lost
> internet connection, you are not notified as well. 
> The "Saving..." notification is shown virtually forever.

Sid-G asked be if this is worth a separate report. It is, and it's bug 41466.

As for the rest, this bug report seems a duplicate of bug 47184: due to bug 45894 and friends (TUX tries never to make you wait for loading or saving), it's impossible to give immediate feedback about the result of attempted saving of translation.

Proofreading doesn't have any saved indication and that's bug 45555.
Comment 6 Rainer Rillke @commons.wikimedia 2013-09-09 10:10:15 UTC
(In reply to comment #5)
> As for the rest, this bug report seems a duplicate of bug 47184:
It's useless getting a warning at the end, when trying to close the tab/page if this warning can't include the reason why saving is not done yet. (This is technically not possible)

The extension should immediately display a big bang! "One translation could not be saved because ..." instead of silently ignoring all errors until you want to quit.

The badtoken error is something the translate extension can solve without any user interaction: 1) /w/api.php?action=tokens 2) evaluate whether it is an anon/IP-token or 2a) /w/api.php?meta=userinfo; if LogIn lost proceed as described at Bug 48775#c4 otherwise 3) retry saving.
Comment 7 Tisza Gergő 2014-04-24 05:57:22 UTC
> Sid-G asked be if this is worth a separate report. It is, and it's bug 41466.

The fix for bug 41466 is now merged, and I haven't seen that specific error message since then; the situation did not improve, though. When the request times out, the little tag saying "Saving" changes to "Not saved" (hard to notice), but there is absolutely no way to retry, not even if you change the translation.

This bug makes translating over a slow connection an extremely painful experience.
Comment 8 Tisza Gergő 2014-04-24 06:07:48 UTC
> there is absolutely no way to retry, not even if you change the translation.

Can't reproduce this part reliably, most of the time I can save again after editing. I have definitely seen this the save button get stuck a few times, but I don't know what prompted it.
Comment 9 Purodha Blissenbach 2014-04-24 11:13:28 UTC
(In reply to Tisza Gergő from comment #8)
> I have definitely seen this the save button get stuck a few times,
> but I don't know what prompted it.

I've never seen somethng else - maybe connection speed is a key to the "decision" - or rather the timelyness of a server reply? If so, it would be easily fixed - after the time out that displays "not saved" also unlock the "save" button.
Comment 10 Nemo 2014-08-09 00:05:15 UTC

*** This bug has been marked as a duplicate of bug 69314 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links