Problem: The client was experiencing issues with translating Elementor templates using WPML. Initially, they used String Translation for an h3 heading widget and a text widget within the template, but the heading widget content was not being indexed for translation. Solution: We advised the client to use WPML's Translation Management tool instead of String Translation for translating Elementor templates. This approach ensures that the layout and content remain consistent across different languages, only translated. If changes in layout per language are needed, making a copy of the template into other languages is recommended. For further guidance, we provided links to our documentation on how to use WPML with Elementor: https://wpml.org/documentation/plugins-compatibility/elementor/
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: The client is using Elementor Pro and wants to translate sections created as Elementor Templates while maintaining the visual layout in both languages. They are encountering an issue where the base language is incorrectly set, and they are unsure if using String Translations is the correct approach for translating these templates. Solution: 1) To maintain the same layout in every language, we recommend following this documentation on translating Elementor Templates with WPML: https://wpml.org/documentation/plugins-compatibility/elementor/ 2) If different layouts per language are desired, this documentation provides the best approach: https://wpml.org/documentation/plugins-compatibility/elementor/creating-different-elementor-templates-per-language-with-wpml/ 3) If the translated template does not display correctly on the frontend, ensure to provide WPML support debug information from your site by following these steps: https://wpml.org/faq/provide-debug-information-faster-support/ 4) Check if the template was translated manually or automatically. If automatic, try making a small change in the default language and re-translate manually. Verify if the WPML editor shows any content for translation, as some widgets might not be compatible with WPML.
If these steps do not resolve your issue or if the documentation links are outdated, we 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 open a new support ticket at WPML support forum.
