Problem: If you're experiencing issues where new components added to an existing page in English are not automatically added to the German version of your website, despite using full automatic translation, this might be due to specific settings. Solution: We recommend checking your WPML settings to ensure that they are configured to: 1. Translate Everything Automatically; 2. Publish right away without reviewing; These settings can be found under WPML > Settings. Additionally, it's possible that the content that was automatically translated is waiting for approval. You can verify this in WPML > Translations.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us directly through our support forum.
Problem: You are trying to display a page in German, but despite translations being present in the translation editor, they do not appear on the page. Instead, texts are still in French. Solution: If you're experiencing this issue, we recommend checking if you have installed the String Translation addon, which is essential for translating page content with Elementor. You can install this addon by going to Plugins > Add new > Commercial. After installation, re-translate your page. Additionally, it's a good practice to make a backup before installing new plugins.
Please note that this solution might be outdated or not applicable 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. If the issue persists, please open a new support ticket.
Problem: The client was experiencing an issue where importing content in different languages (EN, DE, FR) using WP All Import did not create translations but instead created new posts, even with the string translation plugin disabled.
Solution: We advised the client to ensure that the 'Unique identifier' used in the import process is indeed unique for both the template and settings. This identifier should be a unique value/field from the CSV/XML file being imported. We recommended using a new field created solely for this purpose, as outlined in our documentation:
After ensuring the unique identifier is set correctly, the import should then create the translations as expected.
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 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 open a new support ticket in the WPML support forum.
Problem: If you're trying to translate the label of a Custom Post Type (CPT) created with the JetEngine plugin for a multilanguage site and can't find where to do it. Solution: 1. Go to WPML > Settings and under 'Post Type Translation', set the translation preference for your Post Type to "Translatable". 2. Navigate to WPML > Theme and Plugins Localization. 3. Select the JetEngine plugin and scan for strings within the plugin. 4. Once the scan is complete, move to WPML > String Translation. 5. Search for the name of your CPT. 6. If the name appears, click on the "+" icon next to it to add a translation.
If the name doesn't appear in the String Translation, it might be registered as an Admin string. In this case, you need to register the string for translation by following the instructions in our guide:
