Bug #15260
closedCyrillic characters in text record hedlines
0%
Description
Configuration: forced utf-8, DB utf8_general_ci
After entering of a long cyrillic headline in the head field of a text record, for example: "㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑" and saving, error message is generated:
"102: These fields are not properly updated in database: (header) Probably value mismatch with fieldtype."
At the same time the headerline is changed: "㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑㦑 /></td> </tr> <tr bgcolor="
(issue imported from #M1982)
Updated by Karsten Dambekalns almost 19 years ago
Have you set the field size multiplication in the install tool, All Settings? Here's the description:
[multiplyDBfieldSize]
Double: 1-5: Amount used to multiply the DB field size when the install tool is evaluating the database size (eg. "2.5"). This is useful if you want to expand the size of fields for utf-8 etc. For western european sites using utf-8 the need should not be for more than twice the normal single-byte size (2) and for chinese / asian languages 3 should suffice.
This should/might help.
Updated by old_hygro almost 19 years ago
$TYPO3_CONF_VARS["SYS"]["multiplyDBfieldSize"] = '3'
doesn’t changes the behaviour. The header is rejected after the 63-th cyrillic character and a part of the HTML code (!) of the Pagecontent tooll is append instead.
Updated by Dmitry Dulepov almost 19 years ago
I can confirm that cyrillic letters work properly if you set "multiplyDBfieldSize" to 2 and use utf-8 as BE charset (configurable in istall tool). This is tested with typo3 3.7.0, 3.8.1 and 3.9.0-dev.
Alternatively use windows-1251 and russian language in BE.
This bug relates to misconfoguration of typo3, I think it should be closed.
Updated by Karsten Dambekalns almost 19 years ago
After changing the "multiplyDBfieldSize" setting, did you do a database COMPARE in the install tool? Just to make sure you didn't miss that (important) step...
Updated by old_hygro almost 19 years ago
Sorry for the newbie posting.
The point was that I expected an “automatic” size correction.
I confirm that the problem was in short field sizes.
Updated by Karsten Dambekalns almost 19 years ago
This was EBKAC, wrong configuration.