# Charset import bug

**URL:** https://community.kinsta.com/t/charset-import-bug/5609
**Category:** Bug Reports
**Created:** [October 22, 2025, 9:45am UTC](https://community.kinsta.com/t/charset-import-bug/5609 "2025-10-22T09:45:20Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Luca\_Ottolini](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/luca_ottolini/32/5113_2.png) [@Luca\_Ottolini](https://community.kinsta.com/u/Luca_Ottolini)
#### Post date: [October 22, 2025, 9:45am UTC](https://community.kinsta.com/t/charset-import-bug/5609/1 "2025-10-22T09:45:20Z")

</div>

**Q: Date/Time this occurred (Provide your time zone also)**  
**A:It keeps happening**.

**Q: DevKinsta Version**  
\*\*A:\*\*2.13.5 (2.13.5.9020)

**Q: OS Version**  
**A:MacOS** 15.6.1 (24G90)

**Q: Docker Desktop Version**  
\*\*A:\*\*4.22.0 (117440)

**Q: Were any error codes or messages observed? If so, what were they?**  
**A:**

**Q: Detailed Description of the Problem**  
**A:When importing a site with different charsets, some languages will not import properly (screenshots attached)**

 ![charset_bug](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/f/f2039f13cd61ff0d315697e260b8255b57a6957a.jpeg)

---

<div class="post-metadata">

### Author: ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [October 22, 2025, 2:09pm UTC](https://community.kinsta.com/t/charset-import-bug/5609/2 "2025-10-22T14:09:47Z")

</div>

Hello there 👋

Did you check wp-config on DevKinsta against the wp-config on the site from where you pulled?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/5/5217619d0c7d8fc2109bc4dc29a5b62ac52baaba.png)

You can try changing to utf8mb4 (charset) and changing collation to utf8mb4\_unicode\_ci.

Let me know if it helps.

Kind regards!

---

<div class="post-metadata">

### Author: ![Luca\_Ottolini](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/luca_ottolini/32/5113_2.png) [@Luca\_Ottolini](https://community.kinsta.com/u/Luca_Ottolini)
#### Post date: [October 29, 2025, 10:02am UTC](https://community.kinsta.com/t/charset-import-bug/5609/3 "2025-10-29T10:02:53Z")

</div>

Hey Vladimir, thank you!  
wp-config files were basically the same, with no DB\_CHARSET or DB\_COLLATE set.

Tried adding  
`define(‘DB_CHARSET’, ‘utf8mb4’);`  
and  
`define(‘DB_COLLATE’, ‘utf8mb4_unicode_ci’);`

as suggested, but it didn’t work.

I then tried with `define('DB_CHARSET', 'latin1');` and it worked. Not sure if I need to add those two rows on the Kinsta website?

Thanks again!

---

<div class="post-metadata">

### Author: ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)
#### Post date: [October 29, 2025, 12:12pm UTC](https://community.kinsta.com/t/charset-import-bug/5609/4 "2025-10-29T12:12:50Z")

</div>

Hello @Luca_Ottolini 👋

I’m glad to hear that ‘latin1’ charset worked. I would advise pushing back to staging site on Kinsta servers to see if it will perform correctly, not manually modifying charset on live or staging.

Confirm by pushing the site back to staging and then if it works, when you push live the charset will be set to latin1 during the push.

Kind regards!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/8/80f8c4e56fecc02327a0964e6bf63a716483529f.png) [@system](https://community.kinsta.com/u/system)
#### Post date: [November 1, 2025, 12:13am UTC](https://community.kinsta.com/t/charset-import-bug/5609/5 "2025-11-01T00:13:42Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.