Red Hat Bugzilla – Bug 880879
Undo button causing repeated save failures and other weirdness
Last modified: 2013-02-25 23:06:15 EST
Description of problem:
I encountered a failed save operation when trying out the undo-button on a message that I translated just before. After that failed save, I seem to be unable to save that entry no matter what I do (bar reloading the whole page, which I haven't tried yet)
[12:09:07] Save FAILED: id 182189
[12:09:25] Save FAILED: id 182189
[12:09:39] Save FAILED: id 182189
... (some succesful operations on other strings)
[12:14:38] Save FAILED: id 182189
I reloaded the browser's page now, and the troublesome entry appears translated/approved.
It maybe related to bug 873525
(In reply to comment #1)
> I reloaded the browser's page now, and the troublesome entry appears
Does this mean it's saved even though the notification says failed? I can see a bunch of translation history entries within minutes
(In reply to comment #3)
> (In reply to comment #1)
> > I reloaded the browser's page now, and the troublesome entry appears
> > translated/approved.
> Does this mean it's saved even though the notification says failed? I can
> see a bunch of translation history entries within minutes
Possibly. What I did was somthing like this:
1) Entry was untranslated, I translated as "ABC" and saved successfully.
2) I moved on to different entry and translated something else
3) Came back to original entry and changed translation to "ABC test" - I *think* this save operation still succeeded, although not entirely sure now.
4) I then changed the translation back to "ABC", but this save operation produced the error message of failed save.
5) Tried again multiple times to save the translation "ABC", it kept failing. The entry was highlighted in blue indicating unsaved changes
After the page reload the correct translation "ABC" was shown, but I can't tell from which save-operation that translation comes exactly.
Where in those steps did you use Undo? And by that did you mean the Cancel Changes button? Or was it the history button?
(In reply to comment #5)
> Where in those steps did you use Undo? And by that did you mean the Cancel
> Changes button? Or was it the history button?
No, you're right - I missed that. I used the "Undo" button at step 4. (Which now confirms that the save in step 3 must have worked). So I wanted to use the "Undo" button to change the translation back from "ABC test" to "ABC", which failed.
Sorry for the confusion, I didn't pay too much attention at the time, not expecting to having to try to reproduce.
Thanks Hedda, but I'm still not clear on what button you pressed. What do you mean by the Undo button in this case?
Oh, that Undo button! Duh, sorry! I forget we'd finally implemented that.
If I use Undo for step 4, it undoes 'ABCtest' and changes it back to 'ABC' (in the database, if you refresh the page or look at the TM results you can see it), but it leaves the field on the screen empty. Then if you type something, the 'ABC' suddenly appears. It still saves okay for me, so I can't reproduce this bug, but we certainly need to look at Undo.
cannot reproduce it. But I did fix the blank field symptom (sign for CodeMirror refresh) after undo.
Fix commit in : https://github.com/zanata/zanata/commit/50d04fc713711b5e62db0d26aab529028b3ce49b
VERIFIED with Zanata version 2.1-SNAPSHOT (20121206-1113)