-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
All add-ons have been removed #11539
Comments
Everything is fine, add-on settings are only in the base component for the project and from it it is copied to the rest of the components. |
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.
|
Without that users can be confused that their previously installed add-ons are gone. Fixes WeblateOrg#11539
#11552 will add links to other scopes of add-ons to make it more straightforward to find them. |
Without that users can be confused that their previously installed add-ons are gone. Fixes WeblateOrg#11539
Without that users can be confused that their previously installed add-ons are gone. Fixes #11539
Describe the issue
All add-ons have been removed throughout the weblate. All addons are missing. The worst problem is with the automatic translation add-ons, because I am unable to reconstruct in which components it was enabled (it was included in a dozen or several dozen components).
The big problem is the "Update PO files to match POT (msgmerge)" add-on, here about 400 components had different settings
I haven't tried to reconfigure these addons yet, because I hope it will be possible to reproduce it.
Five days ago everything was still working.
I already tried
Steps to reproduce the behavior
Expected behavior
No response
Screenshots
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
5.5.2 — 498e77fb241e962ff85541eed05f7fca63ffc5fd -- 5.5.2 — [498e77f](https://github.com/WeblateOrg/weblate/commits/498e77fb241e962ff85541eed05f7fca63ffc5fd)Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: