Last modified: 2014-06-27 09:16:36 UTC
THis is my first report, I'm green here! My first translation of Blockly strings intro newly approved marginal language (Hrx = Riograndenser Hunsrückisch / a var. of German) in Translatewiki.net didn't get saved - and so I will have to copy and paste all my work string by string onto Chromium where it works :( Unfortunately this will take another bunch of hours of work because it didn't/doesn't save my hours of work done on IE ... https://translatewiki.net/w/i.php?title=Special:Translate&group=out-blockly-0-all&language=hrx
I'm afraid there isn't enough information to investigate this bug. I would need to know the errors (shown in yellow when unsaved messages are opened) or snippets from actual ajax requests.
The yellow error was just the usual "unknown error", the user said. How get "snippets from actual ajax requests" in Internet Exploder?
Paul: What are steps to reproduce this problem? For how long didn't you save? Which amount of strings? Anything that would be helpful to reproduce or narrow down the problem would be helpful.
Paul: Could you please answer comment 3?
(In reply to Andre Klapper from comment #3) > Paul: What are steps to reproduce this problem? For how long didn't you > save? Which amount of strings? Anything that would be helpful to reproduce > or narrow down the problem would be helpful. On my end the problem has been solved for some time now, I thought I reported back. Anyway, what happend is that I wasn't aware that once you leave a window such as this https://translatewiki.net/w/i.php?title=Special:Translate&group=mediawiki&language=hrx&filter=%21translated&action=translate open and inactive for a period of time (at least a couple hours, I'm not sure how long is too long), when you return and continue translating strings ... it will indicate that it is SAVING your new work ... that is, it appear as if your translations are indeed being saved but they ARE NOT BEING SAVED. That "SAVING" operation (that is, for each new line of translation you do) will actually never get completed - and so, in fact, you have to reload the page, loose all your work (in case you've done a lot of pages, like I did the first time), and do everything once again. I know that this work can be done off line, except that I still have not taken the time to read up on that, learn how its done, find out if it is something I should and or would like to be doing. Right now working online is working for me, I have got a lot done. Thanks for checking back with me.
(In reply to Paul Beppler from comment #5) > when you return and continue translating strings > ... it will indicate that it is SAVING your new work ... that is, it appear > as if your translations are indeed being saved but they ARE NOT BEING SAVED. Ok, so the advice here is always to use a freshly loaded Special:Translate. Where should we document this information? We have several bugs here: 1) [INVALID?] Special:Translate "expires"; 2) when it "expires", you're not told so, while you should refresh the page (bug 48775, bug 48657); 3) if you don't, random things happen, from lost edits to edits saved with your IP, with no option to retry (bug 48773); 4) the unsaved translations warning is unreliable (bug 47184, 47119); 5) the "Saving..." indicator generally lies (no specific bug report).
Closing this report because there are already bugs for many of its aspects.
