After update on OTRS 5 I have a problems with Russian symbols in notification.
When I put the Russian text into notification and save it - after that all symbols are change on ????
https://www.dropbox.com/s/def8zuotuae1n ... 5.png?dl=0
I looked into mysql, and some tables was with incorrect coding, I changed it on utf-8_general_ci - but it not helped.
I tried to reboot all and create the new notifications, but it's not working.
[SOLVED] Problems with RU-encoding in notifications
Moderator: crythias
[SOLVED] Problems with RU-encoding in notifications
Last edited by zionlook on 04 Jun 2016, 21:49, edited 1 time in total.
Re: Problems with RU-encoding in notifications
Solution:
Not all tables changed encoding in utf8_general_ci, some of the tables and their structure stay in old encoding.
Must change:
1) Basic charset of otrs database on utf8_general_ci
2) Table charset notification_event on utf8_general_ci
3) Table charset notification_event_item on utf8_general_ci
4) Table charset notification_event_message on utf8_general_ci
5) Check charset of varchar fields in notification_event (must be utf8_general_ci)
6) Check charset of varchar fields in notification_event_item (must be utf8_general_ci)
7) Check charset of varchar fields in notification_event_message (must be utf8_general_ci)
Not all tables changed encoding in utf8_general_ci, some of the tables and their structure stay in old encoding.
Must change:
1) Basic charset of otrs database on utf8_general_ci
2) Table charset notification_event on utf8_general_ci
3) Table charset notification_event_item on utf8_general_ci
4) Table charset notification_event_message on utf8_general_ci
5) Check charset of varchar fields in notification_event (must be utf8_general_ci)
6) Check charset of varchar fields in notification_event_item (must be utf8_general_ci)
7) Check charset of varchar fields in notification_event_message (must be utf8_general_ci)