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:
