Task #34297
Update references to $TYPO3_CONF_VARS['BE']['forceCharset']
| Status: | Closed | Start date: | 2012-02-26 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Chris topher | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 4.7.0 |
Description
some TS options like config.renderCharset and config.metaCharset refer to the option forceCharset in install tool or point out iso-8859-1
Related issues
History
#1 Updated by Chris topher over 3 years ago
- Target version set to 4.7.0
#2 Updated by Chris topher over 3 years ago
- Assigned To set to Chris topher
Summary of the effect of these changes:
- If
$TYPO3_CONF_VARS['BE']['forceCharset']is set to the value "utf-8", the user should just remove this line from his localconf.php. - All values other than "utf-8" will prevent TYPO3 from running and will trigger an error. If another value is used, the user should proceed to the Update Wizard in the TYPO3 Install Tool to update his configuration. Since the backend and the database will communicate "thinking" that they use the charset UTF-8, he must make sure that they really do. Otherwise he will create a charset mix in his database, which will be hard to fix later. Our Wiki page on UTF-8 conversion has more information on how to fix an affected environment accordingly: http://wiki.typo3.org/UTF-8_support
And the charset fallbacks have been changed from iso-8859-1 to utf-8, e.g. for "notification_email_charset". I will include this here as well.
#3 Updated by Chris topher over 3 years ago
- Subject changed from Remove references to forceCharset to Update references to $TYPO3_CONF_VARS['BE']['forceCharset']
#4 Updated by Chris topher over 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Committed in r1170.
#5 Updated by Chris topher over 3 years ago
- Status changed from Resolved to Closed