Problem: You are using WPML with the default language set to German and a secondary language of English, and you want to configure WPML so that automatic translations use British English (en_GB) instead of American English (en_US). You are unsure if automatic EN-GB output is possible or if the system defaults to EN-US for automatic translation. Solution: Currently, WPML does not support a separate option for British English (en_GB) in automatic translations; it defaults to American English (en_US). This limitation is not specific to WPML but is due to the capabilities of major automatic translation engines like Google Translate, DeepL, Microsoft Translator, and Amazon Translate, which only support a generic English version, effectively American English. You can check the currently available languages for automatic translation here.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is experiencing issues with the translation of Elementor Container links in WPML. Specifically, the 'Container Link URL' and 'Container Custom Attributes' fields are missing in the WPML Translation Editor for both pages and Elementor library templates. This inconsistency affects the multilingual functionality of the site. Solution: We recommend the following steps to address the issue: 1. Ensure that the WPML and Elementor plugins are up to date. 2. Verify the XML configuration for Elementor widgets in the
<wpml-config>
file to ensure all necessary fields are correctly defined for translation. 3. Implement PHP registration in the functions.php file as per WPML standards to support custom attributes and link translations. 4. If inconsistencies persist, clear WPML caches, rebuild packages, reset String Translation and ATE. 5. Disable all potentially conflicting plugins and enable the REST API to check if the issue resolves. If these steps do not resolve the issue, it may be due to a known bug or require further investigation. 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 at https://wpml.org/forums/ for personalized assistance.
