Database encoding not utf-8 in default
After installation I realised that some special character like 'ő', 'ű' displayed as '?' in MUC history.
The MySql data table muc_history and msg_history is not UTF-8. I set the tables and rows to 'utf-8-general-ci'
The online delivery okay, the special characters arrive, but the offline messages, and MUC history is still problematic.
After I set the encoding, the Web admin broke down when I try to join room, with special chars in room log. Few rows are arrive then:
xmlns="jabber:x:delay" from="email@example.com/DESKTOP-P1LTIN2"/></message' <-broken XML content, end of response...
Non-web client connection still okay, connected, send MUC messages.
I reinstall the DB, without any content I set the encoding to utf-8
After send a special char in message at web admin muc room, I get this:
.org/protocol/httpbind" xmlns:xmpp="urn:xmpp:xbosh" secure="true" from="chat.medveklub.com" ack="9595270"
xmpp:version="1.0"><message xmlns="jabber:client" from="firstname.lastname@example.org/tsztes" to="admin
@chat.medveklub.com/244775514-tigase-2" type="groupchat">őú<delay xmlns="urn:xmpp:delay"
the stanza is broken, and the BOSH connection stop.
Added by István Tóth over 3 years ago
I fixed the database problem with this steps:
- (MySQL 5.5.1) Add 2 lines at etc/mysql/my.cnf
character-set-server = utf8
collation-server = utf8_general_ci
- restart Mysql server
$ service mysql restart
At mysql console (probably not necessary)
ALTER DATABASE tigasedb DEFAULT CHARACTER SET utf8
I rename muc_history table to muc_history2 table just for sure
restart Tigase server
join a room - the muc_history table automatically created in UTF-8
All the special chars are okay
Web admin room history display still error with broken XML stanza! (you have to refresh & log in again)
Client software okay
Web client with stanza.io and websocket connection okay.