• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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