Project

General

Profile

Actions

Bug #24582

closed

Accept alternative notations for setDBinit

Added by Steffen Gebert over 13 years ago. Updated over 5 years ago.

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

100%

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

Description

The error messages and deprecation log entries could be improved.

E.g.

This TYPO3 installation is using the $TYPO3_CONF_VARS['SYS']['setDBinit'] property with the following value:
SET NAMES 'utf-8'
It looks like UTF-8 is not used for this connection.
Everything other than UTF-8 is deprecated since TYPO3 4.5.

So please tell me, WHAT you expect! (it's SET NAMES utf8 without the quotes and hyphen (dunno how this got into my config.. ;-))

(issue imported from #M17046)


Files

17046.diff (1.41 KB) 17046.diff Administrator Admin, 2011-01-15 00:12

Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #24160: UTF-8 by default: Message on upgraded version should be styled and should tell what the problem isRejected2010-11-22

Actions
Related to TYPO3 Core - Feature #18501: Enable UTF-8 by defaultClosedMichael Stucki2008-03-26

Actions
Related to TYPO3 Core - Bug #24968: Pagetree inline editing produces wrong characters with special chars and without forceCharset=utf-8Closed2011-02-05

Actions
Related to TYPO3 Core - Bug #41596: Content of $TYPO3_CONF_VARS['SYS']['setDBinit'] is completely overruled / ignoredClosed2012-10-04

Actions
Actions

Also available in: Atom PDF