Project

General

Profile

Actions

Bug #22964

closed

Wrong handling of entries in textarea fields in install tool - may break installation

Added by Jochen Weiland over 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Category:
-
Target version:
-
Start date:
2010-06-22
Due date:
% Done:

0%

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

Description

When entering any data with multiple lines in textareas in the "All configuration" setting of the install tool (these are: setDBinit, binSetup, defaultUserTSconfig, defaultTypoScript_constants, defaultTypoScript_editorcfg), the line breaks are converted incorrectly. For example, when entering

A
B
C

after saving this will become

a'.chr(10).'b'.chr(10).'c

which could break the TYPO3 installation completely

Tested with PHP 5.2.13 and 5.3.1, Firefox and Safari

This may be related to issue 0012514

(issue imported from #M14825)


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #21501: Install Tool duplicates values of textarea fieldsClosedSteffen Kamper2009-11-09

Actions
Related to TYPO3 Core - Bug #22893: Core: Could not initialize DB connection with query "SET CHARACTER SET utf8 ...ClosedChris topher2010-06-15

Actions
Has duplicate TYPO3 Core - Bug #23009: Installtool bug with escape-signs in ['SYS']['setDBinit']ClosedChris topher2010-06-27

Actions
Actions #2

Updated by Jochen Weiland over 14 years ago

@Georg: this is not a duplicate of http://bugs.typo3.org/view.php?id=12514 which apparently doubled the entries (couldn't reproduce this in 4.3.3) while 14825 is modifying the entries in a way that they no longer take effect.

If you have (or need) something like

SET NAMES utf8;
SET CHARACTER SET utf8;

in setDBinit this will be changed in the install tool to one line:

SET NAMES utf8;'.chr(10).'SET CHARACTER SET utf8;'.chr(10).'

and in the localconf.php to:

'SET NAMES utf8;\'.chr(10).\'SET CHARACTER SET utf8;\'.chr(10).\'';

This is not a valid MySQL command, resulting in not being executed anymore. This could easily lead to a mixture of charsets in the database if not noticed.

Actions #3

Updated by Jan Loderhose over 14 years ago

well it seems as if the solution of 12514 might solve this issue anyway ... ;-)
12514_v3.diff

Actions #4

Updated by Steffen Kamper over 14 years ago

resolved with #21501

Actions #5

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF