Problem: If you're experiencing an error when trying to automatically translate your homepage, where WPML cannot send some of the content to translation because it includes fields that are encoded, we can help. Solution: This is a known issue. We recommend you follow the steps described on our erratum page: https://wpml.org/errata/wpml-cannot-send-base64-encoded-content-to-translation/.
If this solution does not apply to your case, or if it seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
Problem: You are trying to use automatic translations for strings in WPML, but the option to translate automatically is not appearing in String Translations. Instead, you can only add strings to the translation basket, which only allows assigning them to a translator, not to machine translation. Solution: 1. To enable automatic translation for strings, you need to first send them to the translation basket and assign the translation job to a translator (you can assign it to yourself). 2. Then, navigate to WPML -> Translations, start the translation, and use the automatic translation option in the Advanced Translation Editor (ATE). Alternatively, you can install the WPML 4.7 beta version, which includes the option to translate strings automatically. However, ensure you create a full site backup before installing the beta version to avoid potential issues.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we recommend opening a new support ticket at WPML support forum.
