Emoji : Sorry, something went wrong with saving your entry

Hi Marupilamie,
If you updated to 1.6.3, can you confirm that you can now post an emoji in a guestbook entry?

Hi Marcel, sorry but I did not see your message…I’m doing the update…

sorry but it’s always the same

Oh, too bad. I was hoping there was a workaround. But apparently not.
Sorry, I don’t know a solution or workaround.

If I would be less busy I’d love to help debugging

made a fresh wp-install on my webspace and put your version from ftp. still no debug-messages ?? https://web3.server-drome.org/wptest/

Hi Thomas,
I am not sure if this issue can be resolved.
What you can do is go to:
https://www.ads-software.com/plugins/gwolle-gb/developers/
Download the development version, and install that. On the Settings page there should now be a debug tab, where additional info is displayed, and you can test adding an entry.

I am not sure how this can be fixed or worked around. I think the database communication only accepts utf8mb3, but even using set_charset explicitly to utf8mb4 didn’t fix it for marsupilamie.

that gave me: Array ( [character_set_client] => utf8mb4 [character_set_connection] => utf8mb4 [character_set_database] => latin1 [character_set_filesystem] => binary [character_set_results] => utf8mb4 [character_set_server] => utf8 [character_set_system] => utf8 [character_sets_dir] => /usr/share/mysql-community-server/charsets/ )

Thomas, I am sorry, but I don’t know how to proceed here. The problem is not just in the guestbook, but also happens on posts and comments.
I don’t fully understand the problem or what a possible solution could be.

I put an emoji into DB by phpMyAdmin and it worked. On the page it just shows a questionmark so it might be just encoding. It has to be possible because phpMyAdmin is able to do

ok something interesting: if you show up the entry usual there is not the right encoding, but if you post a new entry and after that you get back to the page it shows the emoji. Look at this picture: https://web3.server-drome.org/01.03.png

Hi, this should be fixed in 1.7.0.
Can you confirm?