Welcome to the LimeSurvey Community Forum

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

Email encoding

  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey GmbH Employee
  • LimeSurvey GmbH Employee
More
9 years 3 months ago #115763 by c_schmitz
Replied by c_schmitz on topic Email encoding
Well, if that fixes your problem it means that your data is originally not saved in UTF-8. You will need to check all tables and each field in the tables again for the right collation.
Did you maybe restore the database previously from a backup using the wrong default collation?

Best regards

Carsten Schmitz
LimeSurvey project leader
The topic has been locked.
More
9 years 3 months ago #115765 by kema
Replied by kema on topic Email encoding
This was a downloaded Ubuntu 14.0.4 virtual machine from bitnami with preinstalled Limesurve 141126.

However what I did was to import a *.lss. But I think it was UTF-8 coded.
Not quiet sure. I'm new to both Linux and php so bare with me ;)

I will try to check the tables. From what I can tell in the database backup, default collation is utf8_unicode_ci

/Kenneth
The topic has been locked.
More
9 years 1 month ago #116401 by kema
Replied by kema on topic Email encoding
So...this continues to haunt me.
After the holidays I have downloaded an updated virtual appliance (Ubuntu 14.04 from bitnami). Running it and it works.
Deploying it on an ESX server in DMZ. Browse to the application and bam... there it is the problem again WTF.
So I started thinking..what changed. I accessed the application remotely. Testing it on the newly downloaded virtual appliance and now I can replicate the error.

If I access limesurvey from within the virtual appliance the email is sent with the correct encoding. If I access limesurvey from the "outside" it's sent with the strange charachters instead of å, ä and ö.
Using Chrome from the outside and Firefox from with Linux if it could be of importance.

/Kenneth
The topic has been locked.
  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey GmbH Employee
  • LimeSurvey GmbH Employee
More
9 years 1 month 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
9 years 1 month ago #116428 by kema
Replied by kema on topic Email encoding
Hello!

I'm running build 141229

/Kenneth



The topic has been locked.
  • c_schmitz
  • c_schmitz's Avatar
  • Offline
  • LimeSurvey GmbH Employee
  • LimeSurvey GmbH Employee
More
9 years 1 month 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
9 years 1 month 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
9 years 2 weeks ago - 9 years 2 weeks 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: 9 years 2 weeks ago by paulorcdo. Reason: teste de leitura
The topic has been locked.
More
9 years 2 weeks 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.

Lime-years ahead

Online-surveys for every purse and purpose