TYPO3 Core

Hi. Here is solution for my problem
file class.tslib_fe.php about line 2502
'cache_data' => serialize($data),
change into
'cache_data' => base64_encode(serialize($data)),

linie 1661
$this->config = (array)unserialize($row['cache_data']); // Fetches the lowlevel config stored with the cached data
change into
$this->config = (array)unserialize(base64_decode($row['cache_data'])); // Fetches the lowlevel config stored with the cached data

I think there is lot of issues like above.
I am experiencing no_cache 1 every couple of refresh
Expiration time is default and no_cache is off in config.
If I understand this correctly, no_cache is set to 1 when Typo3 cant read (unserialize) cached data.

How is the USER_INT integrated in TypoScript? Is it nested in another COA_INT/USER_INT object, like e.g. this?
10 = COA_INT
10 {
20 = USER_INT
20 {
...
}
}
This behaviour of the nested *_INT objects was fixed in the lasted release of TYPO3 4.1 and TYPO3 4.2.

This problem has strange solutions.
I've changed
$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;'.chr(10).'SET CHARACTER SET utf8';
into
$TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8';
There is problem with SET CHARACTER SET utf8

I'm experiencing a very similar situation but even with USER objects. Sometimes the USER objects are not rendered into the FE-Cache.

The common factor is having "forceCharset" set to "utf-8" but I didn't set up $TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8;'.chr(10).'SET CHARACTER SET utf8';

I know that's a problem itself because the data isn't stored the right way into MySQL, but it's functional anyway (but the data is getting a double charset conversion).

This should be solved with TYPO3 4.5, utf8 connection is set as default.