Problem: The client was experiencing an issue with the Advanced Translation Editor (ATE) where after completing translations, the page would get stuck on "refreshing translation status". The error logs indicated that "The xliff file could not be read". Solution: We resolved the issue by changing the configuration of the
_elementor_data
field from 'translated' to 'copy'. After making this change, we updated and translated the page. We also adjusted the page title to refresh the ATE, which the client may need to revert back to the original.
If you're experiencing a similar issue, we recommend trying the following steps: 1. Change the configuration of the
_elementor_data
field from 'translated' to 'copy'. 2. Update and translate the page. 3. If necessary, adjust and then revert the page title to refresh the ATE.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.
Problem: The client wanted to know if the pre-configured Chinese (Traditional) in WPML is the same as Yue Chinese (Cantonese written in traditional Chinese) and how to add Yue/Cantonese as a custom language for automatic translations, as it is not currently supported by WPML.
Solution: We clarified that Yue or Cantonese is indeed different from the Chinese Traditional (zh-Hant) supported by WPML's automatic translation. WPML supports Chinese Traditional via Microsoft translation engine, but Yue or Cantonese (Traditional) is recognized as a different language by Microsoft Translator.
To add Yue as a custom language in WPML, we recommended the following guides:
If the custom language is similar to an existing language, it can be mapped to a supported language to utilize spellcheck and automatic translation features. If there is no similar supported language, the client should select "Don't map this language" and will need to translate content manually.
If this solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
If further assistance is needed, please contact us in the WPML support forum.
Problem: The client is using the Oxygen Builder plugin with WPML to build a website and is encountering issues with special characters in French translations. The characters appear correctly in the WPML Translation Editor, but not on the live site. This issue is only present on pages, not posts.
Solution: We acknowledge that Oxygen Builder is not fully compatible with WPML at the moment. We are working with the Oxygen team to improve this. There is a known issue with non-Latin characters being encoded in translations, which might be related to the client's problem. We recommend checking with the Oxygen team if they are aware of this specific issue and if it will be resolved in the upcoming Oxygen 4.7 update. In the meantime, the client has found potential workarounds using code blocks provided by a third party:
First gist: Uses the same template for translations and conditionally displays the correct language using string translations.
Second gist: Offers similar functionality to the first gist but applies it globally.
Please note that these workarounds are not official solutions from the Oxygen team, and they may not be suitable for all users. If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you continue to experience issues, please open a new support ticket with us.
Problem: The client was adding translations for various languages to a page built with Elementor. While most content translated correctly, the basic text editor widget in Elementor did not translate for the Indonesian language, displaying what appeared to be the widget's ID instead. The WPML translation editor showed the text as translated, but it was not reflected on the front end. Solution: We recommended the client to back up their website and deactivate any additional Elementor plugins one by one to identify which one was causing the issue with the text not displaying in the original language. Once identified, we asked the client to install the problematic plugin on a test site we provided (https://rustic-guitar.sandbox.otgs.work) where Elementor and WPML were already set up with English and Indonesian languages. The client was to create a sample page using the widget so that we could check and provide the proper XML code to make the widget translatable with WPML.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please do not hesitate to open a new support ticket. For further assistance, visit our support forum.
