• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue Problem with special chars after migration between plesks

Iuri Carvalho

New Pleskian
Server operating system version
Ubuntu 22
Plesk version and microupdate number
18.0.59
Hello guys!

We are migrating our sites hosed on Plesk Onyx (Ubuntu 16) to Plesk Obsidian (Ubuntu 22). And we are using to plesk migration tool to do this.

We are having trouble with special chars on the database in the new plesk.

In the old plesk I have this:
mysql> SELECT default_character_set_name, default_collation_name FROM information_schema.SCHEMATA WHERE schema_name = "DB";
+----------------------------+------------------------+
| default_character_set_name | default_collation_name |
+----------------------------+------------------------+
| utf8 | utf8_general_ci |
+----------------------------+------------------------+
1 row in set (0.00 sec)

In the new one, the same database:

MariaDB [DB]> SELECT default_character_set_name, default_collation_name FROM information_schema.SCHEMATA WHERE schema_name = "DB";
+----------------------------+------------------------+
| default_character_set_name | default_collation_name |
+----------------------------+------------------------+
| utf8mb4 | utf8mb4_general_ci |
+----------------------------+------------------------+

When I access the page on the new server, the special chars are like these:

prevenção -> correct: prevenção

Anyone already had this situation?

Thanks in advance.
Kind regards,
Iuri Carvalho
 
Back
Top