By User on Sunday, 01 September 2019
Posted in General Issues
Replies 5
Likes 0
Views 759
Votes 0
Hello. After moving to new server and setup it,
comment form doesn't display 90% of emoji smileys (it display only one heart).

I checked documentation and can't find anything strange

What should I do?

Thanks.

Updated: Seems if reset (chose) emoji again (one by one), it'll start to work. But why?
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

It seems like something is not right when you move to new server because those emoticon only stored it as question mark, you can check my attached screenshot below.

Currently I have no ideas why become like this since you did mentioned this only happen after move to the new server.

For now I think you have to edit each of the emoticon and re-save again.
·
Sunday, 01 September 2019 08:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello. Just for information: it happened again after moving to another server.
Also problem with emoji happens with other places: group title for example. It display ????? instead. Thank.s
·
Sunday, 22 December 2019 13:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hm, is it possible for you share with us how you move your old server to new server?

In order to store those emoji in database, your database must support utf8mb4 collation.

And the table column also need to be support for this utf8mb4 collation as well like store those emoji in group title. (screenshot : https://monosnap.com/file/eu4DD5U5ACIJEHSo4pZYNqhNJDe2vj )

By the way, that is not possible to fix it if the database already stored it as question mark.

Do you have your previous backup?
·
Monday, 23 December 2019 11:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello. I converted DB to utf8mb4.
So next time after migration it will works normal? Thanks.
·
Sunday, 05 January 2020 03:44
·
0 Likes
·
0 Votes
·
0 Comments
·
So you mean last time before you migrate, your new database is not configure to support utf8mb4 collation yet?

If that is the case, yes it should work correctly if your new database already configure to support utf8mb4 collation before you do the migration.
·
Sunday, 05 January 2020 10:45
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post