This object is in archive!
German umlauts and other special characters in email subjects are converted to HTML entities
When a response title contains german umlauts (ü ö ä Ä Ü Ö ß) or other special characters (e. g. quotes), they appear as HTML entities in the email subject.
For example, one of our response titles is
- Muss ich den Führerschein "privater" Fahrer kontrollieren?
– containing a "ü" and also the quotes around "privater".
When an email notification for that response is sent, the email subject says
- Auf Ihre Frage "Muss ich den Führerschein "privater" Fahrer kontrollieren?" wurde geantwortet
– the "ü" has been converted to its HTML entity, "ü", same with the quotes (""").
We're on IIS and use SMTP to send emails. Any clue?
Fixed in 2.2 beta release
Fixed in 2.2 beta release
Hello Guido,
Thanks for reporting the problem. We identified it and fix will be provided in the next release.
Hello Guido,
Thanks for reporting the problem. We identified it and fix will be provided in the next release.
Stas,
as our community will be in German we have to classify this as a blocker.
Please at least give us more information, provide a hotfix or estimate a release date.
Stas,
as our community will be in German we have to classify this as a blocker.
Please at least give us more information, provide a hotfix or estimate a release date.
Hotfix will consist of several files. We'll try to provide it to you via email today or tomorrow the latest, as we understand that it's vital for you to have this covered to support German community.
Hotfix will consist of several files. We'll try to provide it to you via email today or tomorrow the latest, as we understand that it's vital for you to have this covered to support German community.
Superb Stas, looking forward to your mail.
As said before – thanks again for coming through with a solution as soon as possible!
Superb Stas, looking forward to your mail.
As said before – thanks again for coming through with a solution as soon as possible!
Guido,
I've sent you email with fixes. Others will receive it in the next release, as it's not critical issue
Guido,
I've sent you email with fixes. Others will receive it in the next release, as it's not critical issue
Hi Stas,
we finally got around to implement the patch you sent and are happy to report everything works fine now! We're wondering why this wasn't included in the 2.1 update, though?
Thanks again!
Hi Stas,
we finally got around to implement the patch you sent and are happy to report everything works fine now! We're wondering why this wasn't included in the 2.1 update, though?
Thanks again!
Guido,
We didn't include it as 2.1 release was live already by the time the patch was provided
Guido,
We didn't include it as 2.1 release was live already by the time the patch was provided
Hi Stas, thanks for the clarification! Looking forward to the next release ;-)
Hi Stas, thanks for the clarification! Looking forward to the next release ;-)
Fixed in 2.2 beta release
Fixed in 2.2 beta release
Replies have been locked on this page!