Bug #19806
closed
wrong encoded String from class.t3lib_tsfebeuserauth.php
0%
Description
this behavior is reproducible in TYPO3 4.3 and TYPO3 4.2.3
If you activate the FE Editiing and try to deleted a record you get a Javascript confirm "Are you sure you want to delete this record?", in german language there is a UMLAUT Problem.
The same message in german "Diesen Datensatz tatsächlich löschen?".
The String ($labelStr) is encoded with $GLOBALS['LANG']->csConvObj->utf8_to_entities() about line 360 in class.t3lib_tsfebeuserauth.php (in TYPO3 4.2.3 line 1023)
testet with $GLOBALS['LANG']->charSet = utf-8 and iso-8859-1
steps to reproduce
1. get german translation from EM
2. TYPO3 4.3 > install sysext fe_edit>Display Edit " and
3. switch yout BE Language to german
4. activate admPanel with the Options "Editing"
Editing"->Display Edit Panels:
5. try to delete a record
(issue imported from #M10114)
Files
Updated by Marcus Krause over 15 years ago
I can confirm this with current svn branch 4.2 and trunk where TYPO3 is using utf-8.
Updated by Bernhard Eckl over 14 years ago
Same issue here (Version 4.2.10). Any solution how to fix that?
Updated by Steffen Kamper over 14 years ago
commenting out the line solves it. I have to make more test to see why this was used. See patch for trunk
Updated by Bernhard Eckl over 14 years ago
I just applied the patch on another system, without change, so the problem there was not solved through the patch.
On the system where it worked it was TYPO3 4.3 (Debian Lenny, PHP 5.2.11) and on the system where it didn't work, it was TYPO3 4.2.10 (Suse Enterprise, PHP 5.2.6).
Updated by Steffen Kamper over 14 years ago
the not working system - which charset do you use there? And how does the alert look there, can you provide a screenshot?
Updated by Xavier Perseguers about 12 years ago
- Category deleted (
Communication) - Assignee deleted (
Steffen Kamper) - Target version deleted (
0)
Updated by Alexander Opitz over 9 years ago
- Status changed from Accepted to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.8)?
Updated by Sven Juergens over 9 years ago
hi Alexander,
yes the problem still exisits, myself forgot this open issue and open a new for the same problem https://forge.typo3.org/issues/63131 .
Sorry for that.
Best Regards
Sven
Updated by Alexander Opitz over 9 years ago
- Status changed from Needs Feedback to Closed
Thanks for feedback will close this one as duplicate of #63131