Dependency Graph View Issue Relation Graph Vertical
related to child of duplicate of

View Issue Details

IDProjectCategoryView StatusLast Update
0005017phpList 3 applicationGeneralpublic18-02-08 14:06
Status resolvedResolutionfixed 
Product Version2.10.2 
Target Version2.10.7Fixed in Version2.10.4 
Summary0005017: Special character "o acute" is displayed as "ó" in text version of a message.
DescriptionI assume, PHPList does the following:

-> you write an HTML-message in the FCKeditor
-> FCKeditor stores this message in ASCII-style in field "message" in table "_message" in the database
-> the send process takes the content of the message field and stores it in the mail's body
-> because the send process fails to convert the HTML-ASCII back to the special chars or another plain text compatible encoding, all special chars are scrambled in plain text messages
-> HTML messages look fine, because modern E-Mail-clients are able to decode the ASCII-part of special characters in HTML-messages

Seems like this is a major bug in the program's send routine. There is a second field in the table "_message" called "textmessage" but this one's empty. Bug or feature?

What do you think?
Additional Informationsolution submitted:

reported to work for German characters.
TagsNo tags attached.



27-02-06 23:24


possible solution:


03-04-06 18:41

reporter   ~0012171

The submitted solution does not seem to work with the current version (2.10.2), we still get the special chars..


08-08-06 18:45

manager   ~0016470

see also


23-10-06 18:15

manager   ~0020318

In the German forum JenGermany reports that special characters like ä, ö, ü, are displayed as ä ö ü in the text version of an HTML message (see )

The following fix apparently solved the problem:

In class.phplistmailer.php on line 61 (function add_text($text)) ,
 $this->Body = $text;

to this:
 $this->Body = html_entity_decode($text ,ENT_QUOTES, 'UTF-8' );

Phplist 2.10.3

configuration page:
Charset for HTML messages: UTF-8
Charset for Text messages: UTF-8


I couldn't reproduce the problem on my installation, but I had USE_MANUAL_TEXT_PART enabled, which might perhaps account for that.


23-10-06 21:17

manager   ~0020325

yes, I can confirm that. Annoying, I thought it had been fixed, but obviously not