Skip to main content

Bug Report: Database Error when saving long UTF-8/Georgian post titles (wpy2_fcom_posts)

Hello FluentCommunity Support Team,

I am experiencing a critical database error when trying to create or update a post using the Georgian language (UTF-8 characters). The issue specifically occurs when the post title is relatively long.

Here is the error logged by WordPress:

WordPress database error: Invalid data. (SQL: update wpy2_fcom_posts set title = 'αƒ™αƒαƒœαƒ™αƒ£αƒ αƒ‘αƒ˜αƒ‘ αƒ›αƒ˜αƒ–αƒαƒœαƒ˜αƒ მეαƒͺαƒœαƒ˜αƒ”αƒ αƒ”αƒ‘αƒ˜αƒ‘ αƒžαƒαƒžαƒ£αƒšαƒαƒ αƒ˜αƒ–αƒαƒͺαƒ˜αƒ Ⴠართო αƒ‘αƒαƒ–αƒαƒ’αƒαƒ“αƒαƒ”αƒ‘αƒαƒ¨αƒ˜, ბაαƒ₯?', meta = 'a:0:{}', wpy2_fcom_posts.updated_at = '2026-06-14 23:42:40' where id = '5')

Observations:

  • The error only triggers with long titles in Georgian. Short Georgian titles or English titles work fine.
  • Looking at the SQL query, it appears the title string is getting abruptly truncated (ending with a ?), which results in the invalid data error.
  • This strongly suggests an issue with how the plugin handles multibyte character length validation before inserting/updating, or a potential issue with the database column length/collation not fully supporting the required string size for multibyte characters.

Could you please look into this bug and let me know if there is a quick filter/hook or a patch available to bypass this truncation issue?

Thank you

Anri Maglakelidze

Tawsif Ahmed RiyadΒ Thank you

Anri Maglakelidze

To help your development team debug this faster, I suspect this is a multibyte string truncation issue.

If the plugin is using standard PHP functions like substr() instead of mb_substr() for title length validation, it will cut Georgian (UTF-8) characters mid-byte. This creates an invalid character (the ? at the end of the query), which the database subsequently rejects. Alternatively, it might be related to the VARCHAR byte limit for multibyte characters.

Since I am preparing to present this platform to investors very soon, this is a critical blocker for our content team. Could you please provide a quick PHP snippet or filter to temporarily bypass this truncation while your team works on a permanent update?

Thanks for your prompt help!

Md. Ariful Islam

Fixed in dev. Thanks

Anri Maglakelidze

Md. Ariful IslamΒ Thank you so much. May I update a plugin?

Md. Ariful Islam

Anri MaglakelidzeΒ It will be update in the next release soon. Stay tuned. Thanks.

Anri Maglakelidze, for an immediate fix, please update the following code lines of app/Services/FeedsHelper.php.

Code lines 560 to 563,

// trim the title if it's too long to 192 chars (multibyte-safe; column is VARCHAR(192) characters)
if (mb_strlen($processedData['title']) > 192) {
    $processedData['title'] = mb_substr($processedData['title'], 0, 192, 'UTF-8');
}

1.00

Anri Maglakelidze

Tawsif Ahmed RiyadΒ Thank you sooo much

Anri Maglakelidze

Tawsif Ahmed RiyadΒ Hi there, is this fixed within v.2.7. version? Thanks

Anri Maglakelidze, yes, fixed.

Anri Maglakelidze

Tawsif Ahmed RiyadΒ Thank youu