Bug #24968: Pagetree inline editing produces wrong characters with special chars and without forceCharset=utf-8 - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Bug #24968

closed

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

Added by Jesper Scheuer almost 14 years ago. Updated over 12 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Target version:

Start date:

2011-02-05

Due date:

% Done:

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 open — 2 closed)

Related to TYPO3 Core - Bug #24582: Accept alternative notations for setDBinit

Closed

2011-01-15

Actions

Has duplicate TYPO3 Core - Bug #33025: empty setDBinit breaks charset in BE page tree

Closed

Steffen Gebert

2012-01-06

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Steffen Gebert almost 14 years ago

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

It works for me..

Actions

Copy link

Updated by Jesper Scheuer almost 14 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

Copy link

Updated by Sascha no-lastname-given almost 14 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

Copy link

Updated by Steffen Gebert almost 14 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

Copy link

Updated by Steffen Gebert almost 14 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

Copy link

Updated by Sascha no-lastname-given almost 14 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

Copy link