Object name is shortened by use of regular PHP string functions which are not correct when we use mutibyte charset, e.g. utf8.

As a result we get broken string with illegal character at the end that sometimes causes SQL errors by the way. Also this setting in site.ini is not working as we expect cause of difference in number of bytes and char count in the word.
[ContentSettings]
ContentObjectNameLimit=

Solution: use mbstring functions instead of strlen() and substr().

Patch for version 2011.5 is applied.

Steps to reproduce

Try to add a name of the object in multibyte charset that has more bytes for saving string than is set in ContentSettings/ContentObjectNameLimit.