Task #35251
For TYPO3 4.7: Update reference to $TYPO3_CONF_VARS['BE']['forceCharset']
| Status: | Closed | Start date: | 2012-03-26 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Francois Suter | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 4.7.0 |
Description
The manual mentions the option $TYPO3_CONF_VARS['BE']['forceCharset']. However, this option has been removed in TYPO3 4.7.
Make sure to update the manual accordingly.
References: #34092 and #34094.
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
Related issues
Associated revisions
Removed mention of "forceCharset" property, resolves #35251
History
#1 Updated by Francois Suter over 3 years ago
- Status changed from New to Accepted
- Assigned To set to Francois Suter
Found a single mention, in the section about FlexForms. Will update it.
#2 Updated by Francois Suter over 3 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1178.
#3 Updated by Francois Suter over 3 years ago
- Status changed from Resolved to Closed