Bug #24582: Accept alternative notations for setDBinit - 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

Watchers (3)

Michael Stucki
Stano Paska
Tobias Liebig

Actions

Copy link

Bug #24582

closed

Accept alternative notations for setDBinit

Added by Steffen Gebert almost 14 years ago. Updated about 6 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 open — 4 closed)

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

Rejected

2010-11-22

Actions

Related to TYPO3 Core - Feature #18501: Enable UTF-8 by default

Closed

Michael Stucki

2008-03-26

Actions

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

Closed

2011-02-05

Actions

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

Closed

2012-10-04

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Steffen Gebert almost 14 years ago

Need feedback from Benni for the Upgrade Wizard thingy

Actions

Copy link

Updated by Michael Stucki almost 14 years ago

Sounds to me like the line with "SET NAMES utf8" was not recognized correctly.

Actions

Copy link

Updated by Steffen Gebert almost 14 years ago

It's because of this check:

!preg_match('/SET NAMES utf8/', $TYPO3_CONF_VARS['SYS']['setDBinit'])

Quotes are not accepted..

Actions

Copy link

Updated by Steffen Gebert almost 14 years ago

Another point, which should be improved is the comment for $TYPO3_CONF_VARS['BE']['forceCharset']

This option is deprecated since TYPO3 4.5,  and will be removed in 4.7. Please use proper tools to set your installation to native UTF-8.

Setting the value to an empty string in the Install Tool results in putting a line

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

into localconf.php (see #24968).
This overwrites the default value of -1. So removing the value from the input field and assuming that then the default is used is not true.

I would state
" -1 is the default value. Set it to -1 or utf-8, which both results in using utf-8, every other setting is deprecated."

Actions

Copy link

Updated by Kurt Gusbeth over 13 years ago

You should use the i-option too:
!preg_match('/SET NAMES utf8/i', $TYPO3_CONF_VARS['SYS']['setDBinit'])

Actions

Copy link

Updated by Peter Kuehn over 11 years ago

Target version deleted (0)

You should use the i-option too:
!preg_match('/SET NAMES utf8/i', $TYPO3_CONF_VARS['SYS']['setDBinit'])

+1 for Kurts point - would have saved me an hour today not to chase a loged problem that was none ;)

Actions

Copy link

Updated by Michael Stucki over 11 years ago

Subject changed from Improve non-UTF8 deprecation log entries / messages to Accept alternative notations for setDBinit
TYPO3 Version set to 6.1

Actions

Copy link