Last modified: 2013-03-19 20:18:50 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 T48062, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46062 - [TUX] Units still labelled "Unsaved" at the end of page translation
[TUX] Units still labelled "Unsaved" at the end of page translation
Status: RESOLVED DUPLICATE of bug 45766
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 45766
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-13 12:24 UTC by Nemo
Modified: 2013-03-19 20:18 UTC (History)
5 users (show)

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


Attachments
Wrong "Unsaved" labels (143.96 KB, image/png)
2013-03-13 12:24 UTC, Nemo
Details

Description Nemo 2013-03-13 12:24:55 UTC
Created attachment 11922 [details]
Wrong "Unsaved" labels

Actually I now see from contributions they are really unsaved, but I didn't have any warning and it just opened next message.
If I click on a row I see a yellow line "Saving the translation failed: Invalid token" and clicking "Save translation" has no effect. No idea what to do.
Comment 1 Niklas Laxström 2013-03-13 13:20:13 UTC
Sounds like dupe of bug 45766.
Comment 2 Nemo 2013-03-13 13:27:31 UTC
(In reply to comment #1)
> Sounds like dupe of bug 45766.

Mostly, but also its handling by the interface is way less than ideal.
Comment 3 Niklas Laxström 2013-03-13 14:35:11 UTC
What makes it less than ideal?
Comment 4 Nemo 2013-03-13 15:05:41 UTC
(In reply to comment #3)
> What makes it less than ideal?

The fact that I get the warning only if I 1) notice the "Unsaved" labels at the end of the job, have a clue what's happening, 2) open the message in consequence, 3) understand that the yellow warning is about something happened before and not about what I just did.
I didn't fail at (1) out of chance, I failed at (2) before filing the bug and at (3) until your comment.
Comment 5 Siebrand Mazeland 2013-03-19 20:18:50 UTC

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

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


Navigation
Links