• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Charset Issue

Robin McDermott

Basic Pleskian
Server operating system version
AlmaLinux 9.5
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update #2
We migrated to a new server in December and have noticed issues with the display of some characters in our web application:

Dvorský

1742300952489.png

Years ago when we had this issue, we added:

AddDefaultCharset ISO-8859-1

in Additional Apache directives to HTTP and HTTPS for each affected domain to overcome a similar problem with "special" characters (to us in North America).

I am wondering if we should be using a different charset? We do translate content into several different languages (Chinese, Japanese, Russian, Polish...) and don't want that to be impacted by any changes.
 
What PHP version are you using? We encountered such an issue when using an old MySQL connector from PHP 5.x.
 
Do your connection collation and charset match the database collation and charset?

SQL:
MariaDB [(none)]> SHOW SESSION VARIABLES LIKE 'character\_set\_%';
+--------------------------+---------+
| Variable_name            | Value   |
+--------------------------+---------+
| character_set_client     | utf8mb3 |
| character_set_connection | utf8mb3 |
| character_set_database   | latin1  |
| character_set_filesystem | binary  |
| character_set_results    | utf8mb3 |
| character_set_server     | latin1  |
| character_set_system     | utf8mb3 |
+--------------------------+---------+
7 rows in set (0.001 sec)

MariaDB [(none)]> SHOW SESSION VARIABLES LIKE 'collation\_%';
+----------------------+--------------------+
| Variable_name        | Value              |
+----------------------+--------------------+
| collation_connection | utf8mb3_general_ci |
| collation_database   | latin1_swedish_ci  |
| collation_server     | latin1_swedish_ci  |
+----------------------+--------------------+
3 rows in set (0.001 sec)
 
Sorry about that. I was under the impression you were getting the data from a database. In this case, the MariaDB part is not relevant.
 
Back
Top