Project

General

Profile

Actions

Bug #24968

closed

Pagetree inline editing produces wrong characters with special chars and without forceCharset=utf-8

Added by Jesper Scheuer about 13 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-02-05
Due date:
% Done:

0%

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

Description

When I edit a pagename in the pagetree and use local letter (f.x. Danish æ,ø,å or German ö) the name is saved incorrectly.

Tested on Safari and Firefox on Mac.
(issue imported from #M17496)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #24582: Accept alternative notations for setDBinitClosed2011-01-15

Actions
Has duplicate TYPO3 Core - Bug #33025: empty setDBinit breaks charset in BE page treeClosedSteffen Gebert2012-01-06

Actions
Actions #1

Updated by Steffen Gebert about 13 years ago

Have you set [BE][forceCharset] = utf-8 in Install Tool?

It works for me..

Actions #2

Updated by Jesper Scheuer about 13 years ago

Works for me too - but then breaks a lot of other stuff - anyways if it a local problem with my intallation let's just close the issue

Actions #3

Updated by Sascha no-lastname-given about 13 years ago

Without forceCharset same problem. Firfox/Mac.

What happens here:
JS change the label after editing correct. Same time the ajax post includes wrong characters. When response arrive the label gets changed again and this time with wrong characters.

Actions #4

Updated by Steffen Gebert about 13 years ago

Okay, I gave it a try. Without the forceCharset setting, the characters are getting wrong, indeed.

Seems like the input on server side is always treated as utf-8.

Actions #5

Updated by Steffen Gebert about 13 years ago

I just checked the code in config_default.php

If forceCharset is not changed in localconf.php, then it uses utf-8.

Could you please search in your localconf.php for the following line:

$TYPO3_CONF_VARS['BE']['forceCharset'] = ''

The backwards-compatibliity layer for this option presets it to -1 in config_default. So if you set it to empty in the Install Tool, then it assigns '', instead of restoring the default value of -1.
This results in using the BE-user dependent charset. If this line is removed, then the BE uses utf-8 (which is recommended anyway.. however it should also work without it).

Could you please proove my theory of the existance of this line?

Actions #6

Updated by Sascha no-lastname-given about 13 years ago

When i delete line $TYPO3_CONF_VARS['BE']['forceCharset'] = '' the installtool shows me utf-8 and it works without problems, but why should i use this as normal user even if it says "NOTICE: This option is deprecated since TYPO3 4.5".

Actions #7

Updated by Steffen Gebert about 13 years ago

Yes ;)

Actions #8

Updated by Steffen Gebert about 12 years ago

  • Status changed from Accepted to Closed
  • Target version deleted (0)
Actions

Also available in: Atom PDF