Project

General

Profile

Actions

Defect #33649

closed

Ascii code in the 'Description' causes 500 error

Added by Sreeraj Puthiyedath over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

Try entering t the ascii corresponding to code U+1F844 in the description section causes a 500 error.

U+1F844


Related issues

Is duplicate of Redmine - Feature #31921: Changes to properly support 4 byte characters (emoji) when database is MySQLClosedGo MAEDA

Actions
Actions #1

Updated by Holger Just over 4 years ago

  • Is duplicate of Feature #31921: Changes to properly support 4 byte characters (emoji) when database is MySQL added
Actions #2

Updated by Holger Just over 4 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Sometimes (especially when using an older database with MySQL), the underlying database only supports the storage of up to three-byte UTF-8 characters. However, some characters (such as the LEFTWARDS HEAVY ARROW) require four bytes of storage.

To be able to enter those characters, you would need to upgrade your existing database to support 4 bute characters. This means you need to change the collation of the rows from `utf8` to `utf8mb4`. To be ablt to do that, you also need to use row_format = DYNAMIC and the Baracuda file format).

Please see #31921 and http://blog.andriylesyuk.com/4-byte-utf-8-problem-in-redmine-and-how-to-fix-it/ for some details on how to migrate your existing database. Before performing these changes, please make sure that you have a full and working backup of your database so that you can revert to that backup in case anything goes wrong.

Actions

Also available in: Atom PDF