Problem: You are trying to merge two sites, one in English and one in Hebrew, into a single WPML-powered site, using the English site as the base. Solution: 1) Set the English version as your main default language. 2) Export the Hebrew content from the second website and import it into your main site. Unfortunately, there isn't an integrated function in WordPress/WPML for this task, so you might need to use additional plugins or tools. 3) If you wish to maintain separate domains for each language, set up a Multi-Domain configuration. You can find detailed instructions here: How to use WPML with different domains per language. If you encounter difficulties with content import, consider hiring a certified contractor. You can find our certified partners here: WPML Contractors.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client is confused about why some strings in the string translation panel are marked as English when the native language in the WPML settings is French. Solution: We explained that most plugins register their strings by default in English. We recommended that the client manually change the source language of any string by following the steps in our documentation:
Problem: The client was unable to translate the string 'NOS SERVICES' from French to English on their website's footer, even though the string appeared to be translated in the WPML String Translation interface.
Solution: 1. We suggested checking for duplicates of the string that might need translation and recommended removing the untranslated string and re-registering it by: - Enabling the "Look for strings while pages are rendered" option in WPML > String Translation. - Visiting the page with the untranslated string to trigger the registration. - Searching again in WPML > String Translation for the string. 2. If the string was not found, we advised checking if it was added as admin text and provided a link to the relevant documentation: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
3. Upon receiving access to the client's site, we discovered that the footer was created with Elementor and provided steps to translate Elementor templates, along with a link to the documentation: https://wpml.org/documentation/plugins-compatibility/elementor/#translate-elementor-templates - We added the Elementor template 'pied de page' to the translation basket in WPML > Translation Management. - Sent it for translation and assigned the translation to the admin user. - Instructed the client to translate the content from the provided link.
We also shared additional resources for learning about Automatic Translation and Translation Editor Options.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket by visiting our support forum: https://wpml.org/forums/forum/english-support/
Problem: The client is experiencing an issue where images in a gallery created with an Elementor carousel widget are not appearing in the translated version of the page, even though the gallery field has been marked as translatable. Solution: If you're using the same images across different languages, we recommend setting the image field preference to "Copy" to ensure images are copied to the translated post. Here are the steps we took to resolve the issue: 1. Edit the post in the secondary language (e.g., French). 2. Set the field preference to "Copy". 3. Click "Apply". 4. Click "Update". 5. Edit the Elementor template "Elementor Page unique #1592". 6. Update the translation to refresh the widget Image Carousel settings on the translated page. After following these steps, the image gallery should now display correctly on the translated post. For more detailed guidance, please refer to our documentation on translating custom fields.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client has imported new translated XLIFF files but is facing an: the pages do not appear translated in the backend despite being translated on the frontend.
Solution: We explained that since the translations were imported using the WPML Classic Translation Editor, they would not be displayed in the Advanced Translation Editor as it runs on our server. To edit existing translations, the client should enable the Classic Translation Editor by navigating to WPML > Settings > Translation Editor > Enable Classic Translation Editor. For more information, refer to our documentation: https://wpml.org/faq/why-arent-my-translations-showing/.
If the provided solution does not seem relevant or if there are further issues, please do not hesitate to open a new support ticket by visiting the WPML support forum.
Problem: The client is experiencing issues with importing a .zip file containing translated XLIFF files. After importing, the pages are not translated, and attempting to approve the translations results in an error message stating that the action does not apply to any of the selected translation jobs. Solution: We have identified that the XLIFF file format provided by the translator differs from the format exported from WPML. We recommend contacting the translator and requesting that they export the translation again, ensuring that the XLIFF file matches the format of the file originally exported from WPML. For guidance on configuring XLIFF file options, please refer to our documentation:
