Problem: The client is using Elementor templates and WPML for translating page content. They have a template (container template) translated by WPML, but on the translated page, the content of this template appears in the original language instead of the translated version. Solution: We have identified that the Envo Extra plugin has its own implementation for the
[elementor-template id="ID"]
shortcode, which is causing the issue with WPML. We recommend the following workaround: 1. Edit the
4. After making this change, clear the cache and make minor edits to the page. Then, try re-translating it to see if the issue is resolved. We also suggest asking the plugin/theme author to join our Go-Global program: https://wpml.org/documentation/support/go-global-program/
Please note that this solution might be outdated or not applicable to your case. If it doesn't help, 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 the problem persists, please open a new support ticket: https://wpml.org/forums/forum/english-support/
Problem: If you're using the Shortcode widget within Elementor and notice that the content does not appear in the WPML page translation window, and translations saved in WPML String Translation are reset to the original language when you modify the page translation again, you are encountering a known issue. Solution: We acknowledge this behavior is expected at the moment due to the way numbers-only shortcodes are handled. They are not visible in the Advanced Translation Editor (ATE) and any translations done via String Translation will be overwritten if the page is edited again in the ATE. Currently, we recommend manually translating the content of the Shortcode widget as a workaround. We are working on a fix for this issue, but in the meantime, manual translation is the suggested method.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
