Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

Email encoding

More
10 years 7 months ago #116423 by c_schmitz
Replied by c_schmitz on topic Email encoding
Please update to the latest version as this was fixed on Nov 17th and release a few days later.
See bugs.limesurvey.org/view.php?id=9358

Best regards

Carsten Schmitz
LimeSurvey project leader
The topic has been locked.
More
10 years 7 months ago #116428 by kema
Replied by kema on topic Email encoding
Hello!

I'm running build 141229

/Kenneth



The topic has been locked.
More
10 years 7 months ago #116430 by c_schmitz
Replied by c_schmitz on topic Email encoding
In your original posts you stated that you are running 141126 ?
Have you cleared your browser cache after update?

Best regards

Carsten Schmitz
LimeSurvey project leader
The topic has been locked.
More
10 years 7 months ago #116433 by kema
Replied by kema on topic Email encoding
Hi!
Now it's working. Clearing the cache solved it. :woohoo: :woohoo:

Thanks!
The topic has been locked.
More
10 years 5 months ago - 10 years 5 months ago #117871 by paulorcdo
Replied by paulorcdo on topic Email encoding
Brazilian Solution:

in common_helper.php:

if ($emailcharset!='iso-8859-15')
{
if ($emailcharset=='utf-8')
{
$from=mb_convert_encoding($from,$emailcharset,'utf-8');
$body=mb_convert_encoding($body,$emailcharset,'utf-8');
$subject=mb_convert_encoding($subject,$emailcharset,'utf-8');
$sitename=mb_convert_encoding($sitename,$emailcharset,'utf-8');
}
else
{
$from=mb_convert_encoding($from,$emailcharset,'iso-8859-15');
$body=mb_convert_encoding($body,$emailcharset,'iso-8859-15');
$subject=mb_convert_encoding($subject,$emailcharset,'iso-8859-15');
$sitename=mb_convert_encoding($sitename,$emailcharset,'iso-8859-15');
}
}


Paulo
Last edit: 10 years 5 months ago by paulorcdo. Reason: teste de leitura
The topic has been locked.
More
10 years 5 months ago #117887 by kema
Replied by kema on topic Email encoding
Hi paulorcdo!

Thar was my quick and dirty solution as well. Then they found the bug and solved it in the following version.
Clearing the browser cache solved it for me.

Regards
/Kenneth
The topic has been locked.
Moderators: tpartnerholch

Lime-years ahead

Online-surveys for every purse and purpose