Problem: You are experiencing intermittent issues with WooCommerce product URLs when using WPML. Specifically, product URLs in a secondary language occasionally use the category slug from the default language, leading to mixed-language URLs and causing infinite redirect loops and a 'too many redirects' error in the browser. Solution: 1. Update WCML: Ensure you are using WooCommerce Multilingual & Multicurrency version 5.5.5 or later, as this issue was addressed in version 5.5.3. 2. Check translation settings: Temporarily disable the 'Translatable – use translation if available or fallback to the default language' setting and conduct tests to see if the issue persists. 3. Apply workaround: If the problem continues, consider implementing the code workaround provided on the errata page.
Please note that this solution might be irrelevant if it's 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 is experiencing an issue where products in secondary languages are being incorrectly synced and displayed in their Facebook catalogue, despite being archived in WooCommerce. This issue arises from the integration between WPML and Facebook for WooCommerce. Solution: 1. We confirmed that the 'Facebook Visibility' feature in WPML archives secondary language products as intended, but they are still being synced by Facebook for WooCommerce. 2. Our compatibility team has escalated this as a feature request to the developers of Facebook for WooCommerce. However, they have found that the integration is managed by Facebook for WooCommerce, not WPML. 3. We suggested a potential workaround using a custom filter to prevent syncing of secondary language products:
**** Important! Please make a full site backup (files and DB) before you proceed with those steps**** 4. We also recommend contacting Automatic, the authors of Facebook for WooCommerce, to address this integration issue. If this solution does not resolve your issue or seems irrelevant, 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.
Problem: The client's website was initially translated using the classic WordPress editor. After deciding to switch to the advanced translation editor for adding more languages, they encountered an issue where products, posts, and pages originally created with the WordPress still open in that format. The client is concerned about losing existing translations and the credits used for them if they switch to the new editor for older post IDs. Solution: We explained that switching the translation method for content that was previously translated using the WordPress Editor to the WPML Translation Editor could result in the loss of the old translations, as they would be overwritten. This is because the translations are stored in the translation memory of the WPML Translation Editor and are applied when the content is sent for translation. If the client decides to proceed with switching to the Advanced Translation Editor and uses credits for automatic translation, it is not advisable to switch the translation method back to use the "WordPress Editor". If you run into issues where translations open on the WordPress Editor while you expect the Advanced Translation Editor to open, please revise the right sidebar of the original content inside the WordPress Editor and make sure that the translation method is set to "WPML Translation Editor". Also note, that automatic translations are technically not possible when using the WordPress Editor as translation method.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: The client is experiencing issues with WPML AI skipping content during automatic translation, particularly with content embedded in shortcodes from a theme that uses WPBakery. The client is concerned about whether they are still charged for untranslated content and how to ensure all content is translated without manually defining shortcode attributes.
Solution: We recommend adding a WPML language configuration for the shortcodes that are being skipped. This will allow WPML to recognize and translate the content. You are not charged for content that WPML skips. To configure WPML to recognize your shortcodes, follow these steps: 1. Identify the shortcodes that WPML is skipping. 2. Add a language configuration for these shortcodes. You can find guidance on how to do this in our documentation: Register Page Builder Content for Translation and Overriding Language Configuration Files. 3. If your theme's authors have not created a language configuration file, consider contacting them to request one, or use the WPML Multilingual Tools to automatically register the shortcodes as described here: Multilingual Tools. 4. Perform a scan of your theme and plugins through WPML -> Theme and plugins localization -> Scan the theme (and the parent theme if applicable).
If this solution does not resolve your issue or seems outdated, 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 open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where automatic translations of a product in WPML result in the slug having a '-2' appended, making it different from the original product's slug. Solution: This behavior is expected due to the WordPress API's restriction against duplicate slugs within the same site. When translating a post or page, WPML automatically adds a language code suffix to ensure uniqueness. For more details on managing and understanding slug behavior in translations, we recommend visiting the following documentation:
If this solution does not apply to your case, or if it seems outdated, please open 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, you can always contact us through the WPML support forum.
Problem: If you're experiencing concerns about what happens to translations when you need to delete a string and re-import it due to a plugin bug, you might be worried about losing these translations. Solution: We assure you that you won't lose the string translations. Once a segment is translated, whether it's a string or a segment from a post, it gets saved in WPML's Translation Memory. This means that once saved, you won't need to add the translation again, and you won't be charged if you send the strings for automatic translation again. For more details, you can check the documentation here: How WPML Keeps Track of Your Translations.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client needs a comprehensive guide on translating taxonomies and WooCommerce pages using WPML, especially when automatic translation does not meet their specific needs. They encountered issues where taxonomies were not automatically translated when translating products, leading to incorrect category assignments.
Solution: 1. Taxonomies will be translated automatically along with the posts or products they are assigned to. If you're experiencing different results, we recommend checking your site's settings and providing us with WPML debugging information. More information here: https://wpml.org/de/faq/provide-debug-information-faster-support/
2. For WooCommerce pages, replace any WooCommerce Blocks on the Cart or Checkout page with WooCommerce Shortcodes, as we currently cannot translate new blocks. You can find more about WooCommerce Page Shortcodes here: https://woocommerce.com/document/woocommerce-shortcodes/page-shortcodes/ Strings from these pages can then be translated using WPML > String Translation.
3. Attributes are translated automatically with the product they are assigned to. To translate all global attributes in one job, create a product, assign all available attributes to it, and send the product for automatic translation.
4. If a taxonomy is already translated, it will be synced when translating the post. You can also sync taxonomies at WPML > Taxonomy Translation if WPML recognizes that taxonomies are missing on translated posts.
If the solution provided here does not resolve your issue or seems outdated, 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 open a new support ticket at WPML support forum.
