Thanks for your patience. This is the feedback from our 2nd Tier Support.
WPML automatically checks whether gzip compression and decompression are available. If they are, WPML uses them when storing and retrieving translation data.
If gzip compression was never available on a site, the data is stored uncompressed.
A problem occurs when gzip compression was available at some point, so the data was stored compressed, but later becomes unavailable because it was disabled on the server or the site was moved to a server without it. In that situation, WPML cannot properly read the compressed data, and garbled characters may appear in the Classic Translation Editor.
This scenario is unexpected, and the next WPML version will include a warning to let users know that gzip compression is missing and needs to be enabled.
In this particular client’s case, after updating WPML, running troubleshooting steps, and possibly moving the site between servers, some of the data became double compressed.
The utility plugin I created fixes that issue. It ensures the data remains compressed only once and can be read correctly, but it still requires gzip decompression to be enabled on the server.
One more thing, our 2nd Tier Support mentioned that he sent the wrong file. Could you install this plugin hidden link and run it without the "Dry Run" option? Please backup before you proceed. Also, running this plugin again will not break your Website.
The topic ‘[Closed] Broken characters (like “x?Ž…”)’ is closed to new replies.
