We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I call GET /api/translations/(string:project)/(string:component)/(string:language)/file/ API, and after update it returns 404.
GET /api/translations/(string:project)/(string:component)/(string:language)/file/
User that has token is admin, has all possible permissions.
I checked documentation and source code, noticed new API for ZIP download, but i use old raw one
Should i regenerate token?
No response
Docker container
4.9.1
The text was updated successfully, but these errors were encountered:
Seems repos were "broken" after upgrade. I did pull operation for my repo and it helped.
Sorry, something went wrong.
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
No branches or pull requests
Describe the issue
I call
GET /api/translations/(string:project)/(string:component)/(string:language)/file/
API, and after update it returns 404.User that has token is admin, has all possible permissions.
I checked documentation and source code, noticed new API for ZIP download, but i use old raw one
Should i regenerate token?
I already tried
Steps to reproduce the behavior
No response
Expected behavior
No response
Screenshots
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
4.9.1
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: