Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi 2own! Thanks for the heads up.

    We do have an issued logged for this (#166) and it’s being worked on right now. We will be changing the default CHARSET to utf-8 as well as doing an upgrade routine on the DB for all past entries.

    I expect the fix for this to be released within a few days.

    Hello 2own, just wanted to update you that as of version 1.1.4 the charset issue has been resolved. Please update the plugin and report back if you have any other issues. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Non-latin symbols error’ is closed to new replies.