Possible FIX for API Invalid unicode character sequences

  • Resolved sarahox

    (@sarahox)


    8 years, 1 month ago

    After the update I was getting The API Error Code: Invalid unicode character sequences in 4 out of every 5 published articles.

    Having done nothing different I knew that the unicode error must be a mistake, so I spent the day trying to find what was going on.

    It was actually in the new SECTIONS update, but mostly my fault. I thought that you had to add all of the categories that you wanted in MAIN, in the MAIN section in the SECTIONS settings. You do not, if you don’t want/need different sections, then simply leave it blank and it will instantly go into Main.

    I wanted to reach out since I thought others might do the same, and the error code that it gives, does not match the actual problem. Thought it could help

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Bradford Campeau-Laurion

    (@potatomaster)

    It’s highly unlikely that these two things are related. I wouldn’t want others to think this is a definitive solution. We are looking into the unicode issue separately.

    Plugin Author Kevin Fodness

    (@kevinfodness)

    Hi @sarahox—

    We released version 1.2.3 this week, which includes a fix for what we believe is the most common cause of the invalid Unicode sequences error. Can you update to the latest version and let us know if that fixes your issue, please?

    Thanks!

    Plugin Author Kevin Fodness

    (@kevinfodness)

    I’m going to close this issue for now. If you’re still noticing problems using the latest version of the plugin, please let us know and I can re-open the issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Possible FIX for API Invalid unicode character sequences’ is closed to new replies.

Tags