[TYPO3-core] RFC: #12613: Errors with cache data from DB

Steffen Kamper info at sk-typo3.de
Mon Nov 16 17:05:08 CET 2009


Hi,

This is SVN patch request.

Type: Bugfix

Branches: trunk

BT reference: http://bugs.typo3.org/view.php?id=12613

Problem:
There are several issues where cache data makes problems, eg if 
renderCharset != metaCharset. Then it happens if the cache data has 
special char like an Umlaut, the returned data is corrupted.

Reason is that cache-table use field TEXT for serialized arrays, 
therfore MySQL respect the charset.

Solution: use BLOB instead

Additional (comment from Masi)
In cache_pages the field HTML stores the complete page. Yet this must be 
also a BLOB since Mysql (and other DBs) take it ill if the sent data is 
not in the charset of the column.

To be precise: if you have the DB in utf-8 the content will be truncated 
at the first byte that is invalid in utf8.

This also solves #12549 - No typoscript template found

vg Steffen
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 12613.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20091116/881ae9d6/attachment.asc>


More information about the TYPO3-team-core mailing list