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

[BUG] Translation not working if glossary out of sync #349

Open
borishinzer opened this issue Jul 17, 2024 · 0 comments
Open

[BUG] Translation not working if glossary out of sync #349

borishinzer opened this issue Jul 17, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@borishinzer
Copy link
Contributor

Describe the bug
We noticed that if a glossary is existing, which contains entries, but is out-of-sync with DeepL (the Glossary ID can't be found with DeepL API), translations are not working. The translation will then only contain the original language.

To Reproduce
unsure

Expected behavior
Check against API if Glossary ID is know by DeepL API, otherwise show an error message (eg. as flash message in TYPO3 backend)

Workaround
Manually sync the glossary from the TYPO3 backend.

@borishinzer borishinzer added the bug Something isn't working label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant