Project

General

Profile

Actions

Bug #14455

closed

html entities getting borked at rendering

Added by Franois Prichon almost 20 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
Content Rendering
Target version:
-
Start date:
2004-12-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Html entities may be stored in the field 'fulltextdata' of the indexf_fulltext table. They will be parsed by some htmlspecialchars() function before being rendered in the html page.
ie: we store some à in mysql and it become à

I resolved the problem with this ugly hack :
In class.indexer.php (near line 1300), replace
$fields = array(
'phash' => $this->hash['phash'],
'fulltextdata' => implode($this->contentParts,' ')
);
by
$fields = array(
'phash' => $this->hash['phash'],
'fulltextdata' => html_entity_decode(implode($this->contentParts,' '), ENT_QUOTES)
);
(issue imported from #M618)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #14106: t3lib_cs.php lacks charset->entities conversion for arbitrary charsetsClosed2004-04-26

Actions
Actions #1

Updated by Ernesto Baschny about 19 years ago

Note that html_entity_decode() is only available in PHP >= 4.3.0. So I would be careful to use this.

Actions #2

Updated by Martin Kutschker over 18 years ago

Is this still an issue? Quite some time has passed since the bug has been submitted.

Actions #3

Updated by Christian Kuhn over 15 years ago

Resolved, no change required after three years without requested feedback.

Please reopen if this issue still exists.

Actions #4

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF