Project

General

Profile

Actions

Bug #25369

closed

Upgrade 4.4.x to 4.5.x should unset "setDBinit" and "forceCharset" instead of empty

Added by Stefan Neufeind about 13 years ago. Updated about 13 years ago.

Status:
Rejected
Priority:
Should have
Category:
-
Target version:
-
Start date:
2011-03-21
Due date:
% Done:

0%

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

Description

Upon upgrading the wizard sets "setDBinit" and "forceCharset" to empty strings. However that does not result in the new defaults (UTF-8) being used, but actually does not init the DB and might (if server defaults to latin1) still leave the DB-connection at latin1 which causes other problems.

Commenting out those two settings in localconf.php works fine because TYPO3 then uses the new defaults (afaik as designed/advertised)

(issue imported from #M18004)


Related issues 1 (0 open1 closed)

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

Actions
Actions #1

Updated by Torben Hansen about 13 years ago

If you create an new TYPO3 4.5 installation, then you´ll notice, that "setDBinit" and "forceCharset" are not set, because since TYPO3 4.5 those values have a default setting if not set in localconf.php. If the upgrade wizzard sets one or both values to an empty sting, then your TYPO3 4.4.x installation has´nt been setup correctly to use UTF-8 (e.g. not all table-collations set to utf8_general_ci).

In TYPO3 4.4.x, both "setDBinit" and "forceCharset" must be setup as described in the TYPO3 wiki (http://wiki.typo3.org/UTF-8_support). If this is not the case, that you have to convert your database to UTF-8 before upgrading to TYPO3 4.5

Actions #2

Updated by Stefan Neufeind about 13 years ago

It all worked fine (converted DB before upgrade, changed collation of columns and also of database). It's just that there was no setDBinit-setting before, I then adjusted the DB and upgraded TYPO3 - and at that point the wizard inserted those two settings into localconf.php - but with an empty string (which prevents the UTF-8-default). Removing them worked. I'm just saying that not writing empty strings into localconf.php at all (and people knowing there is a new default which requires DB-adjustment) might be an easier way.

Actions #3

Updated by Michael Stucki about 13 years ago

  • Status changed from New to Rejected
  • Assignee set to Michael Stucki
  • Target version deleted (0)

The behaviour is correct because for upgrades, UTF-8 is not used automatically. It is only the default for new sites.

Actions

Also available in: Atom PDF