TYPO3 Core

Typo3 4.2.1
PHP 5.2.0-8+etch10
MySQL 5.0.32

DB, Typo3-FE & -BE is using utf-8. typo3conf

$TYPO3_CONF_VARS['BE']['forceCharset'] = 'utf-8';
$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;';

mysql> show variables where variable_name like '%char%';
----------------------------------------------------+ | Variable_name | Value |
----------------------------------------------------+ | character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | utf8 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ |
----------------------------------------------------+

Insert a HTML-Element on any page with content "»" is working without problems, as long as "config.no_cache = 1" is set.

After enabling caching "»" results in an unknown symbol (=> ?) and the html-source stored in the field "HTML" in table "cache_pages" is cut off after this point. On next reload the cached (but destroyed) source is delivered to the browser.

If I insert the Symbol by copy&paste from a Website like http://unicode.e-workers.de/entities.php everything works OK. But this is no solution, as for example newscalendar uses "»" and "«" for navigation etc...

I could not reproduce this error on another typo3-installation at the same server, but cannot see any significant difference between the installations.

The field "HTML" in "cache_pages" is "mediumtext", could this issue be related to something like this:

2007-04-02 Michael Stucki <michael@typo3.org>

• Fixed bug #17053: Cache is not saved properly because of charset conflict in the database. Changing the field type of cache_hash.content from mediumtext to mediumblob. To make this work, you need to compare your database in the Install Tool.

=> After changing fieldtype to mediumblob, the whole source is saved into "HTML", but "»" is still an unknown symbol in the FE.
(issue imported from #M9120)