tickets #157459
closed
Descriptions of tickets with special unicode characters included yield "Internal server error 500"
Added by okurz 11 months ago.
Updated 11 months ago.
Description
Observation¶
Descriptions of tickets with special unicode characters included yield "Internal server error 500"
Steps to reproduce¶
- Create a new ticket with with special unicode characters, e.g. the small central dot that
systemctl status outputs before the name of machines or services
- Save the ticket
- Update the description, e.g. add a space
- Try to save the updated ticket
- Observe the error message
Further details¶
- Private changed from Yes to No
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to crameleon
Hi,
thanks for making the ticket.
I found why it works in comments, but not in ticket descriptions:
MariaDB [redmine]> SHOW TABLE STATUS LIKE 'journal_details'\G;
...
Collation: latin1_swedish_ci
...
MariaDB [redmine]> SHOW TABLE STATUS LIKE 'comments'\G;
...
Collation: utf8mb4_unicode_ci
...
I will try to convert the journal_details table to either utf8mb4_unicode_ci, or, if possible, the more modern utf8mb4_unicode_520_ci.
- Status changed from In Progress to Feedback
One backup and a few seconds later
MariaDB [redmine]> ALTER TABLE journal_details CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
Query OK, 249388 rows affected (1.362 sec)
Records: 249388 Duplicates: 0 Warnings: 0
this is now done.
Tested here - both with your systemctl status example and with emojies: https://progress.opensuse.org/issues/157828.
Please confirm on your end as well and let me know.
#157870 looks awesome now. Thanks a lot. You can resolve the ticket if you are happy with it as well.
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
Great, thanks for confirming!
Also available in: Atom
PDF