TYPO3 Core

Workaround:

The lines

    function entities_to_utf8($str, $alsoStdHtmlEnt = FALSE) {
        if ($alsoStdHtmlEnt) {
            $trans_tbl = array_flip(get_html_translation_table(HTML_ENTITIES, ENT_COMPAT, 'UTF-8'));
        }

    function entities_to_utf8($str, $alsoStdHtmlEnt = FALSE) {
        if ($alsoStdHtmlEnt) {
            if (version_compare(PHP_VERSION, '5.3.4') >= 0) {
                $trans_tbl = array_flip(get_html_translation_table(HTML_ENTITIES, ENT_COMPAT, 'UTF-8'));
            } else {
                $trans_tbl = array_flip(get_html_translation_table(HTML_ENTITIES, ENT_COMPAT));
                if (!empty($trans_tbl)) {
                    foreach ($trans_tbl as $key => $entry) {
                        $trans_tbl[$key] = utf8_encode($entry);
                    } 
                }
            }
        }

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/13504

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/13504

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/13504

Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/13504

The effect of this bug are warnings like these in the log (since TYPO3 4.7):

Core: Error handler (FE): PHP Warning: array_flip() expects parameter 1 to be array, null given in /.../typo3_src/t3lib/class.t3lib_cs.php line 819

Core: Error handler (FE): PHP Warning: get_html_translation_table() expects at most 2 parameters, 3 given in /.../typo3_src/t3lib/class.t3lib_cs.php line 819

This happens for example when Indexed Search is indexing a page (in the frontend).

Fix solves it (at least in my test 4.7 environment). Will review it...

Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/16790

I reviewed positively the master patch. I just didn't merge it yet because of the 6.0.0 release merge freeze, so I will ask Helmut if it's ok to do it anyway.

I already prepared a 4.7 backported patch (no cherry-picking possible because of different class names) and pushed it to gerrit. Since the code at this place didn't change between the versions (except the class name), I would merge it as "already reviewed and verified in upper version". No side-effects expected.

Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/16949