Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -
- 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

Tagged: 

This topic contains 45 replies, has 1 voice.

Last updated by Kor 5 months, 1 week ago.

Assisted by: Kor.

Author Posts
November 26, 2025 at 8:24 am #17610348

Kor

Thanks. I've shared this with our 2nd Tier Support.

November 26, 2025 at 4:25 pm #17612878

Kor

Thanks for your reply. Based on the error message. Our 2nd Tier Support mentioned that the error shows that the gzuncompress function is unavailable on your server.

It is a standard PHP function (hidden link), probably because the host has blocked the zlib library or compiled PHP without it.

Please ask your hosting provider to enable it and then let me know how it goes.

November 28, 2025 at 8:39 am #17617448

martinZ-12

Hello Kor,

gzuncompress is enableb.

Let me know please

November 28, 2025 at 8:46 am #17617463

Kor

Thanks for your reply. I've forwarded this to our 2nd Tier Support for further assistance.

November 28, 2025 at 2:30 pm #17618393

Kor

Thanks for your patience. Our 2nd Tier Support applied a fix to your Website and it's working now as shown in the attached screenshot. Please check this test page hidden link

Screenshot_113.png
December 1, 2025 at 4:23 pm #17623369

martinZ-12

Hi Kor,

thank you for taking care of this. The fix really works. Could you please give me the steps on how to fix it on the main website, as support only had access to a copy of the website? In addition, the same problem occurred on other websites. It seems to be a widespread error.

December 1, 2025 at 4:31 pm #17623376

Kor

Thanks for your reply. I’ll check with our 2nd Tier Support to understand how this issue was resolved. In the meantime, if possible, please create a backup and share access to your production site so I can review it further.

December 1, 2025 at 4:40 pm #17623520

Kor

Thanks for your patience. This is what our 2nd Tier Support mentioned. Could you backup and give this a try on your production site?

On the staging site they will find there is a simple custom plugin to fix the problem.
It adds an item to the dashboard Tools menu, which basically has a button to run a script to apply the fix. By default, there is a "dry run" checkbox checked, so the first time you run it, it won't actually update the data, but it should indicate that it will fix it, in which case you can go ahead and uncheck the dry run checkbox and run properly.

December 1, 2025 at 5:43 pm #17623719

martinZ-12

Hello Kor,

thank you for the update.

I would prefer not to provide access to the production site, as I need to keep a clear overview of all actions performed there and apply the fix myself. This will also help me repeat the solution on several other websites where the same issue appears.

Could you please provide:
1. The complete custom plugin your 2nd Tier Support used on the staging site,

2. A detailed step-by-step guide on how to run the fix (including the “dry run” step and the final execution),

3. Any additional notes needed to ensure the fix works correctly on multiple sites.

With this information, I’ll be able to apply the fix on the production site as well as other affected installations.

Thank you very much for your cooperation.

December 1, 2025 at 8:34 pm #17623902

Kor

Thanks for your reply. I noticed the plugin file is no longer available on your staging site. I’ll check with our 2nd Tier Support and get back to you as soon as possible.

December 2, 2025 at 3:55 pm #17627525

Kor

Thanks for your patience.

Please backup the entire site and follow the instructions below.

1. Install and activate this "ICL Translate Field Data Fix" plugin on your Website. hidden link

2. Go to WP > Tools > ICL Translate Fix

3. Uncheck Dry Run

4. Click Run Fix.

Screenshot_148.png
December 3, 2025 at 7:32 am #17629219

martinZ-12

Hello Kor,

thank you very much for the instructions and for providing the plugin. I applied the fix, and everything is now working correctly. I really appreciate your help and the support from the 2nd Tier team.

Thanks again!

December 3, 2025 at 7:32 am #17629221

Kor

Glad that helped. Please mark this ticket as resolved.

December 4, 2025 at 9:16 am #17633142

martinZ-12

Hello Kor,

one more important update:

After applying the fix, everything works correctly until I disable gzuncompress.
Once gzuncompress is disabled, the broken characters issue appears again.

Interestingly, on several other websites where gzuncompress is permanently disabled, the problem does not occur at all.

It seems the issue is tied specifically to how gzuncompress behaves on this particular website.
Could you please check this with your 2nd Tier Support so we can identify a stable, permanent solution?

Thank you!

December 4, 2025 at 9:55 am #17633292

Kor

Thanks for your reply. I've forwarded your feedback to our 2nd Tier Support. I will come back to you once I've feedback.

The topic ‘[Closed] Broken characters (like “x?Ž…”)’ is closed to new replies.