Skip to content
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

Closed
2 tasks done
Geeyun-JY3 opened this issue Jan 28, 2022 · 8 comments
Closed
2 tasks done
Assignees
Labels
enhancement Adding or requesting a new feature.
Milestone

Comments

@Geeyun-JY3
Copy link
Collaborator

Geeyun-JY3 commented Jan 28, 2022

Describe the issue

Source text in history (changes) event is always same as the latest source text. It may confused users.

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

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
image

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

@Geeyun-JY3 Geeyun-JY3 changed the title Source text in history (changes) event is always same as the latest source text Source text in history (changes) event is always the same as the latest source text Jan 28, 2022
@nijel nijel self-assigned this Jan 28, 2022
@nijel nijel added this to the 4.11 milestone Jan 28, 2022
@nijel nijel added the enhancement Adding or requesting a new feature. label Jan 28, 2022
@nijel nijel closed this as completed in 790d8dd Jan 28, 2022
@github-actions
Copy link

Thank you for your report; the issue you have reported has just been fixed.

  • In case you see a problem with the fix, please comment on this issue.
  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

@Geeyun-JY3
Copy link
Collaborator Author

nijel added a commit that referenced this issue Apr 19, 2022
We need to use source string at the time of the change, not current one.

Fixes #7171
@nijel
Copy link
Member

nijel commented Apr 19, 2022

Should be fixed by 10f3c4e

@Geeyun-JY3
Copy link
Collaborator Author

@nijel It seems that this bug is still not completely fixed.
A recent example: https://hosted.weblate.org/translate/f-droid/f-droid/zh_Hans/?checksum=8ffca01dbdaf4d5a#history

@nijel
Copy link
Member

nijel commented Jun 6, 2022

The previous source string was not stored before 790d8dd, so it is expected for old changes to not have matching source string...

@Geeyun-JY3
Copy link
Collaborator Author

Geeyun-JY3 commented Jun 6, 2022

Got it. Thanks for the explanation.

@Geeyun-JY3
Copy link
Collaborator Author

Geeyun-JY3 commented Jun 20, 2022

@nijel Still can reproduce this bug in suggestion-related events.

Example: https://hosted.weblate.org/translate/libretube/libretube/zh_Hans/?checksum=82bebea27ebe8cd8#history
The corresponding source text of the suggestion added in 2022-06-10T12:44:48+00:00 should be There is a new update available. Click okay to become redirected to the update page on GitHub.
image

I guess all the suggestion-related events(Suggestion accepted, Suggestion added, Suggestion removed, Suggestion removed during cleanup) have this bug.
BTW, I think storing the previous source strings may not be enough for the fixes for Suggestion accepted events. A warning dialog may be needed.

nijel added a commit that referenced this issue Jun 20, 2022
This ensures that all expected attributes are present.

Fixes #7171
@nijel
Copy link
Member

nijel commented Jun 20, 2022

That one should be fixed in 4ebf4c9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding or requesting a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants