Advertisement:

Author Topic: Database Error: Incorrect string value  (Read 561 times)

Offline Opsboss

  • Semi-Newbie
  • *
  • Posts: 16
Database Error: Incorrect string value
« on: November 22, 2019, 02:28:10 PM »
We're still using 1.1.21 and in the past few days users have been receiving an error message when attempting to post: "Database Error: Incorrect string value: '\xF0\x9F\x91\x89 S...' for column 'body' at row 1 File: /home/customer/www/windageandelevation.net/public_html/Sources/Subs-Post.php
Line: 1535" Any idea what that's about and how to fix it?

Offline Arantor

  • Resident Overthinker
  • SMF Friend
  • SMF Legend
  • *
  • Posts: 71,982
    • StoryBB/StoryBB on GitHub
Re: Database Error: Incorrect string value
« Reply #1 on: November 22, 2019, 02:34:39 PM »
SMF 1.1 doesn’t support emoji, you need to upgrade to SMF 2.0.15.
Don’t try to tell me that some power can corrupt a person. You haven’t had enough to know what it’s like.

No good deed goes unpunished / No act of charity goes unresented.

Offline Opsboss

  • Semi-Newbie
  • *
  • Posts: 16
Re: Database Error: Incorrect string value
« Reply #2 on: November 22, 2019, 02:39:04 PM »
Thanks. Yeah, I know I need to upgrade. Tried once and it crashed. Apparently I need to upgrade through half a dozen 2.0.xx versions one at a time. I have an actual life and don't presently have the time or patience to do that. Anyway, appreciate the response. We'll try a temporary fix by eliminating emojis.

Offline Illori

  • Project Manager
  • SMF Legend
  • *
  • Posts: 51,617
Re: Database Error: Incorrect string value
« Reply #3 on: November 22, 2019, 02:41:23 PM »
once you upgrade to one version of SMF 2.0.* you can use the package manager to finish the upgrade quickly, that is if you cant upgrade directly to SMF 2.0.15.

Offline Opsboss

  • Semi-Newbie
  • *
  • Posts: 16
Re: Database Error: Incorrect string value
« Reply #4 on: November 22, 2019, 02:46:20 PM »
Thanks. Yes I tried upgrading directly to 2.0.15 and no joy. When I find some time I'll try upgrading to an earlier 2.0.xx version, then on to 2.0.15. But finding the time to do it is a challenge.