-
-
Notifications
You must be signed in to change notification settings - Fork 955
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
No notification when source strings are added or updated #10651
Comments
There is currently no notification for source string being changed. Closest to that is "Unfinished strings exist" as that will trigger when some string will need a translation. |
Any plan to integrate this? Coming from Transifex this is one of the key features, as rarely no translators are polling weblate for changes. It keeps them engaged. |
This seems like a duplicate of #5602. Can you please review that and close this if this is really the case? |
Not really, mine is more about notifications and not about pending tasks. |
Or is there another way a translator who watches a project gets a notification when a source string has change or is added? |
@laoneo The notification for new string is there (New string is available for translation), the notification when source string changes is not there. @Aga-C Unfortunately, we're not talking about a bug here, but about a missing feature. If you see a bug, please open a separate issue for that and provide more information (especially what notifications you have configured). |
Thanks @nijel , but I do not get a mail when a new string is added either after a git rebase from the github webhook. |
@nijel how big is the chance that you will implement this feature request that when a source string is update that notification mails are going out? With this change you can catch up to the big providers like transifex or crowdin as this is an important feature to keep the translators engaged. |
This doesn't work on self hosted weblate. Should I open a bug report for this? Just that I do not miss here something. I'm adding a new string to the monolingual file and push it to the git repo. Then weblate updates but no mail is going out that there are new strings available for translation. |
This makes the history more clear (it doesn't start with "String changed in the repository") and allows to trigger new string notification on such event. See WeblateOrg#10651
You're right, the strings added in the repository do not trigger the notification, #10659 should address this. |
This makes the history more clear (it doesn't start with "String changed in the repository") and allows to trigger new string notification on such event. See #10651
This comment was marked as off-topic.
This comment was marked as off-topic.
@nijel is it possible the issue wasn't completely solved? I'm testing locally version Rolling back to version 4.18.2 works. That is, with the same app data folder and database, adding a new string to the repo successfully sends a |
The issue indeed isn't completely solved as it is still open. Do you see "String added in the repository" event in the string history? |
This way it is also triggered via bulk_create and thus for events that were created during repository update. We reuse post_save emitting logic which is already present in bulk_create for the fedora messaging integration. See WeblateOrg#10651
#11002 should fix the new string notification not being sent. |
This way it is also triggered via bulk_create and thus for events that were created during repository update. We reuse post_save emitting logic which is already present in bulk_create for the fedora messaging integration. See #10651
Thanks, so only update is missing and then can this issue being closed? |
Yes. |
Ok, then I wait with closing this issue. |
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the issue
When a source strings get's updated or added in a component through a git commit in the en-GB "Monolingual base language file", then no notification mail goes out. In the notification settings I'v set "New string is available for translation" and "String was changed" to instant notification. Do I miss here something or is this a bug?
I already tried
Steps to reproduce the behavior
Expected behavior
A notification mail goes out to the user.
Screenshots
Exception traceback
No response
How do you run Weblate?
Docker container
Weblate versions
5.3
Weblate deploy checks
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: