• Resolved Johan Yourstone

    (@jyourstone)


    Hello,

    It seems that you can’t use smileys in entries when the site is using HTTPS. I tried posting an entry in our guestbook with smileys and just got an error message saying there was a problem when posting.
    If I try the exact same thing on our staging site without HTTPS it works.

    Regards,
    Johan Yourstone

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Marcel Pol

    (@mpol)

    Hmm, it works for me.

    Can you share the url of the website?

    Thread Starter Johan Yourstone

    (@jyourstone)

    I’m not really sure what else it could be since the staging and live site are almost identical except for the SSL.

    Staging site guestbook link: https://staging.yourstone-keramik.se/gastbok/
    Live site guestbook link: https://www.yourstone-keramik.se/gastbok/

    Smileys are disabled on the live site right now since it doesn’t work. The weird thing is that it sends an e-mail to admin even though an error is displayed when posting.

    Let me know if you need me to enable smileys on the live site for you to test.

    Plugin Author Marcel Pol

    (@mpol)

    Ah, it doesn’t save it.

    Could you go to Dashboard > Guestbook > Settings > Debug-tab ?
    Then save the test-entries and see if that works.

    Also, can you paste some of the information on that page?

    It does seem that the webserver uses current software, with PHP 7.0. Not sure why it doesn’t accept Emoji characters.

    Thread Starter Johan Yourstone

    (@jyourstone)

    Default test: Success
    Emoji test: Failed

    PHP version:	7.0.17
    MySQL version:	5.6.35-log
    MySQL teckenupps?ttning:	MySQL teckenupps?ttning: utf8mb4
    MySQL kolumn-teckenupps?ttning utf8
    MySQL / MySQLi:	mysqli
    MySQL variabler:	Array ( [character_set_client] => utf8mb4 [character_set_connection] => utf8mb4 [character_set_database] => latin1 [character_set_filesystem] => binary [character_set_results] => utf8mb4 [character_set_server] => latin1 [character_set_system] => utf8 [character_sets_dir] => /usr/share/mysql/charsets/ )

    Here’s from the staging site:

    Default test: Success
    Emoji test: Success

    PHP version:	7.0.17
    MySQL version:	5.6.35-log
    MySQL teckenupps?ttning:	MySQL teckenupps?ttning: utf8mb4
    MySQL kolumn-teckenupps?ttning utf8mb4
    MySQL / MySQLi:	mysqli
    MySQL variabler:	Array ( [character_set_client] => utf8mb4 [character_set_connection] => utf8mb4 [character_set_database] => latin1 [character_set_filesystem] => binary [character_set_results] => utf8mb4 [character_set_server] => latin1 [character_set_system] => utf8 [character_sets_dir] => /usr/share/mysql/charsets/ )
    Thread Starter Johan Yourstone

    (@jyourstone)

    Maybe something to do with utf8 vs utf8mb4?

    Plugin Author Marcel Pol

    (@mpol)

    Yes, but it is very strange that it does work on the Debug page.

    You could see if you ca change the database collation from utf8mb4 to utf8 (which is really utf8mb3). That setting should be in wp-config.php.

    Plugin Author Marcel Pol

    (@mpol)

    By the way, my test server has the same settings for the database…

    Plugin Author Marcel Pol

    (@mpol)

    Ah, I see it now. On the live server it failed. And the column uses utf8. Something went wrong during install or upgrade. Did you move the website recently?

    Plugin Author Marcel Pol

    (@mpol)

    Replying again ??

    If you did move the website or database, and you haven’t upgraded Gwolle since that move… What you can do is run the update function manually. You can just go to gwolle-gb/gwolle-gb.php and change this line:
    define('GWOLLE_GB_VER', '2.1.5');
    to:
    define('GWOLLE_GB_VER', '2.1.5.1');
    That will run the update function (I tested) and will try to change the column charset for the Gwolle tables. Afterwards you should see this on the same debug page.

    If you use Query Monitor, you will see the function call for maybe_convert_table_to_utf8mb4() twice.

    Also, this version number will never be used, so the next update should run fine. Or if it makes you feel better, you change it back to what it was.

    I am off for the evening. I hope it works out well for you.

    Thread Starter Johan Yourstone

    (@jyourstone)

    Thanks for the help!

    I was able to get it working by going into PHPMyAdmin and changing the charset manually to utf8mb4.

    I had a company merge our old website with the new one, so that’s when the charsets were changed I guess.

    Thanks again!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Smileys not working on HTTPS?’ is closed to new replies.