Problem: There is a discrepancy in product variation names and IDs when viewed by different users in different languages. Specifically, the product 'Cake pop' with variation ID 1509 and SKU EVO7006 is incorrectly displayed as 'Pretty plump' with variation ID 107 and SKU EVO7003 for the German shop manager, while it displays correctly for the English-speaking account. Solution: We recommend updating the original language settings and ensuring both translations are correctly synchronized. Here are the steps we took: 1. We made a small edit to the original languages. 2. We updated both translations to ensure consistency across different user views. If you're experiencing this issue, we suggest following these steps to correct the product variation display in different languages. If the problem persists, or if this solution seems outdated or irrelevant to your case, please visit our known issues page and check for any related issues. Also, ensure you have the latest versions of themes and plugins installed. If needed, do not hesitate to open a new support ticket through our support forum for further assistance.
Problem: If you're experiencing issues where you cannot see the category pages in other languages and it throws an error, Solution: We recommend removing the translations for product category slugs and then adding them again as they were before. This action can resolve the issue of category pages not displaying correctly in different languages.
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 problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: If you're experiencing issues with your WordPress site where problems occur in the site’s default language and WPML does not alter the content, it might not be related to WPML but to other plugins like Elementor. Solution: We recommend reaching out to the author of the Elementor widget or element you are using to display images and text, as the issue might be due to their code. Additionally, ensure that all WPML plugins are updated to the latest version. You can update your WPML plugins to version 4.7.5 by navigating to Plugins → Add New → Commercial tab.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to ensure that product category images appear in the translated languages on your site, but the images do not appear in these languages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML >> Settings > Custom Term Meta Translation. 2. Set the
thumbnail_id
field to Copy. 3. Re-save the product categories in the default language to copy the thumbnail field into secondary languages.
This should resolve the issue and the category images should now appear correctly in the translated languages. If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend that you open a new support ticket.
Problem: The client is trying to translate the CartFlows plugin using WPML, including URLs, checkout pages, and fields, but faces issues with Elementor not loading and certain elements not translating correctly. Solution: 1. Create a CartFlow in the Original Language: Build your CartFlow as usual in the default language. 2. Set Post Types as Translatable: Go to WPML > Settings > Post Types and set cartflows_step and cartflows_flow to translatable. 3. Duplicate the CartFlow for Translation: Use WPML's duplicate feature to create a copy in the secondary language. More details here: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/ 4. Translate Independently: Edit the duplicated CartFlow using the WordPress Standard Editor. In the Language box, click Translate independently. More details here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/ 5. Clone Each Step: Use CartFlows' "Clone Step" feature for each step in the flow. Instructions here: https://cartflows.com/docs/clone-flow-step-in-cartflows/ 6. Delete Original Steps and Save Translations: Save the translated texts locally, delete the original steps, and then copy the translated texts back into the appropriate fields. 7. Edit and Update Steps: Update titles and links for each step, then save the changes.
If these steps do not resolve your issue or if the solution seems outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum: WPML Support Forum
Problem: You are unable to translate locked strings on your site using WPML. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to WPML -> String Translation. 2. Search for "actions". 3. Delete the admin strings "[wlfmc_options][button-display][wishlist_under_table]0". 4. Check the wishlist page.
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 reported that variable products translated into Spanish using WPML were showing as out of stock, despite previous solutions that involved updating products in the original language and then re-saving them after minor edits.
Solution: We recommended the following steps to address the issue: 1. Navigate to WooCommerce > WooCommerce Multilingual > Attributes tab. 2. Select the attribute from which the variations were created. 3. Click the button at the bottom to synchronize the attributes. 4. Go to the Status tab and click on Troubleshooting. 5. Select the options shown in this screenshot (https://prnt.sc/oKKMHMZPhIWT) and start the synchronization. 6. If the '_stock' field is set to 'not translatable' in WPML → Settings → Custom Fields Translation, change it to 'Copy'. 7. Clear site and browser caches.
If these steps do not resolve the issue, we suggested a deeper investigation which might require temporary admin access to the site for further troubleshooting.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client has a custom post type called Projects, and the images are not syncing across translations. Solution: 1. Verify if the images are added through a custom field. If so, ensure the custom field is set to "copy" in the translation settings. 2. If the images are not added through a custom field, navigate to WPML->Settings->Media Translation and run the function that duplicates or translates images to other languages. 3. If the issue persists, check the widget, block, or custom field used for these images. Since they are set through Elementor, without backend access, further specific guidance cannot be provided. 4. Change the translation preference of the custom fields to "copy" using the Expert mode. Then, make a small edit to the content of the project so WPML can detect the changes and retranslate, which will copy those fields in other languages.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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 https://wpml.org/forums/forum/english-support/.
Problem: You are trying to translate a shipping method on your site, but the string doesn't appear translated. Solution: First, ensure that there might be another instance of the same string under a different domain. We recommend you go to WPML > String Translation. At the bottom, check the box labeled "Look for strings while pages are rendered" and then visit the shipping page where the string is displayed. After this, return to the string translation page to see if another instance of this string has loaded. If you do not find it, proceed to Translate texts in admin screens and search for the string there. For more detailed guidance, you can visit our FAQ on this topic at https://wpml.org/faq/why-arent-my-translated-strings-showing-up-on-the-front-end-of-my-site/ If these steps do not resolve the issue, it might be due to an incompatible string which would require further debugging.
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 problem persists, please open a new support ticket for personalized assistance.
Problem: You are trying to sync stock on your site using WPML, but the stock is not synced in the translated language, showing as out of stock. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Take a backup of your site's database in case something goes wrong. 2. Navigate to WooCommerce -> WooCommerce Multilingual & Multicurrency -> Settings -> Troubleshooting link. Here you can find the direct link to this screen: Troubleshooting Settings 3. Select the following options: - Sync product stock quantity and status (synchronizing minimum stock between translations) - Fix translated variations relationships - Sync removed product meta from original products to translations 4. Click the 'Start' button and wait for the process to finish. 5. Refresh the translated product and check if the problem is fixed.
Please note that this solution might be outdated or not applicable to your 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: If you're experiencing issues translating product information with nested HTML tags in WPML, and find that your translations are not saving, it might be due to incorrect HTML formatting in the editor. Solution: First, ensure that all nested tags in your original content are correctly opened and closed. Here's how you can check and correct the formatting:
<code><br /><img src="path/to/image.jpg" alt="Descriptive text for the image"><br /></code>
After correcting the original content, apply the same formatting to the translation: 1. Select the text and click the Marker icon to format it (screenshot: https://prnt.sc/Verip2kUFWOl). 2. If the translation still doesn't save, delete the translation for that specific segment. 3. Copy the original content into the translation to ensure all tags are accurately copied. 4. Translate the text within the tags, ensuring not to edit or remove the tags themselves.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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. Additionally, you can open a new support ticket for further assistance at https://wpml.org/forums/forum/english-support/.
