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

Incorrect translation status after machine translation (XLIFF-exported pages) #2318

Closed
MizukiTemma opened this issue Jun 13, 2023 · 2 comments · Fixed by #2323 or #2418
Closed

Incorrect translation status after machine translation (XLIFF-exported pages) #2318

MizukiTemma opened this issue Jun 13, 2023 · 2 comments · Fixed by #2323 or #2418
Assignees
Labels
‼️ prio: high Needs to be resolved ASAP. 🐛 bug Something isn't working
Milestone

Comments

@MizukiTemma
Copy link
Member

MizukiTemma commented Jun 13, 2023

Describe the Bug

Translation status of "currently in translation" pages does not transit correctly after machine translation.

Steps to Reproduce

  1. Go to a page.
  2. Export the page for translation in a language for which machine translation is allowed
  3. Machine translate it by bulk action.
  4. See the status remains "currently in translation" with clock icon.

Expected Behavior

After machine translation the status changes to "machine translation" (and the robot icon).

Actual Behavior

Aftter machne translation the status remains "currently in translation" (with the clock icon).

Additional Information

Related issue #2319

Traceback
@MizukiTemma
Copy link
Member Author

It seems the problem is more generall: when Redis is activated, the icon doesn not transit qucikly (sometimes transits after a while/some other operations, sometimes remains unchanged) although the change is actually saved in the database.

@timobrembeck
Copy link
Member

It seems the problem is more generall: when Redis is activated, the icon doesn not transit qucikly (sometimes transits after a while/some other operations, sometimes remains unchanged) although the change is actually saved in the database.

Thanks for investigating this issue. In this case, I'd say we re-open it and make sure to invalidate the cache correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
‼️ prio: high Needs to be resolved ASAP. 🐛 bug Something isn't working
Projects
None yet
2 participants