-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source text in history (changes) event is always the same as the latest source text #7171
Comments
Thank you for your report; the issue you have reported has just been fixed.
|
@nijel Still can reproduce this bug. |
We need to use source string at the time of the change, not current one. Fixes #7171
Should be fixed by 10f3c4e |
@nijel It seems that this bug is still not completely fixed. |
The previous source string was not stored before 790d8dd, so it is expected for old changes to not have matching source string... |
Got it. Thanks for the explanation. |
@nijel Still can reproduce this bug in suggestion-related events. Example: https://hosted.weblate.org/translate/libretube/libretube/zh_Hans/?checksum=82bebea27ebe8cd8#history I guess all the suggestion-related events(Suggestion accepted, Suggestion added, Suggestion removed, Suggestion removed during cleanup) have this bug. |
This ensures that all expected attributes are present. Fixes #7171
That one should be fixed in 4ebf4c9 |
Describe the issue
Source text in history (changes) event is always same as the latest source text. It may confused users.
I already tried
Steps to reproduce the behavior
Shown in everywhere the event shown, such as
History
tab of any target string translate page, changes page.Expected behavior
Show the source text at that time.
Screenshots
Example: https://hosted.weblate.org/translate/weblate/hosted-error-pages/zh_Hans/?checksum=92048f2895471655
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
No response
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: