-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Language of acceptance email #5554
Comments
@alex-cstl That's a really good point. We didn't think through that use-case, so thanks for that! (It's interesting that it hasn't come up before, but I suppose most folks typically don't split languages across users that way. So it seems to me, the emails should go out in the language of the recipient, UNLESS there is no value for the locale of that user, in which case it should be set to the locale in Settings > Localization. |
@snipe Indeed, the emails should go out in the language of the recipient. If there is no value, it should use the site's main and default language. But speaking of the "no value" case, does it really happen? The very first time I went into "Edit Your Profile", the language was already set to French, the same as the web site's default language. Thanks for looking at the issue and have a great day! |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Looks like the newer version of Laravel will handle this more elegantly. (I had some janky, wacky nonsense staged for develop, but was hoping not to have to use it.) |
Cool! Can't wait to test this out! We're still trailing in the update department... still using Snipe-IT 4.3.0... As we speak, Hugo is trying to get the "LDAP Sync" working because right now, it crashes while attempting to read and import all of our users from our AD. He has a ticket on-going with your team in order to find a fix. A "work-around" has been found but it is not elegant and it is time-consuming (since we have to sync all of our OU one by one...). Thanks! |
@alex-cstl This update would be in v5, which isn't out yet, so no need to rush :) |
) * Fixes #5554. Language of mail doesn't show as intended by the settings.
Dear All, we are encountring same issue. I arranged user's language as Romanian, and I am using Turkish. When I send acceptance mail, it sends a Turkish one. |
Hello there i was used "Email List of All Assigned " buton to notification for users at Turkish Language. I updated snipe it at Version v6.2.3 - build 11936 (master) then the notification couldn't reach in turkish, only english. I tried the change localization settings and profile settings english to turkish but never changed received mails languages. |
Describe the bug
Our school board is french and we must use french softwares for our users. So our Snipe-IT website is set to be in french ("Default Language" under the "Localization" menu).
By personal preferences, I decided to set my own personal profile to be in english. This should only affect ME and no one else.
But I noticed that if I check out an asset to a user, the check out email (acceptance) the user receives is written in ENGLISH, even though the main website is set to display in FRENCH and the user's profile is also in FRENCH. So, it seems Snipe-IT is relying on the language of MY profile (ENGLISH) to decide what language the email should be sent in, instead of the website's Default Language.
To Reproduce
The receiving user should receive an email and this email should be in the language of the sending user.
Expected behavior
I expect Snipe-IT to send check out emails (acceptance) to users using the MAIN and DEFAULT language set in the general preferences (under the Localization menu in the options), which is FRENCH in our case.
Screenshots
Not really applicable
Server (please complete the following information):
Desktop (please complete the following information):
Error Messages
Not applicable
Additional context
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: