-
-
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
Backup does not restore #8905
Comments
The problem is that there is an empty string in the translation memory (inside {
"source": "",
"target": " ",
"source_language": "en",
"target_language": "pt_BR",
"origin": "librariesdirect/librariesdirect",
"category": 10000003
} Removing it should fix the import. Still, Weblate should handle this gracefully. |
Thanks, I've removed the faulty entry from my JSON file and the import was now successful. |
nijel
added a commit
to nijel/weblate
that referenced
this issue
Mar 14, 2023
5 tasks
nijel
added a commit
that referenced
this issue
Mar 14, 2023
Thank you for your report; the issue you have reported has just been fixed.
|
nijel
added a commit
that referenced
this issue
Aug 22, 2023
The check was previously done at the unit level what skipped some of the entries. Fixes #8905
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue
I am trying to import a backup from a project exported on another Weblate instance. This is not successful and yields the following cryptic error message:
Unfortunately I do not understand what this means and failed to find and fix the problem in my backup ZIP manually.
Both instances are running the same weblate version. Two other projects have successfully exported and imported in this combination of instances.
I already tried
Steps to reproduce the behavior
Expected behavior
The backup should import successfully.
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
Docker
Weblate versions
Both instances run 4.16.2
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: