Problem: You are trying to translate Kadence elements using ATE, but are encountering issues where items unexpectedly get flagged for later, and translations are being removed. This problem makes manual translation seem easier compared to using ATE. Solution: We have identified that this is a known issue affecting other clients as well. We are currently developing a fix, which will be included in an upcoming release. Unfortunately, we do not have a specific timeline for this release yet. For more details, you can check the related known issue here: https://wpml.org/errata/ate-some-segments-are-automatically-marked-as-flagged-for-later/
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking other 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue where the gallery slider on the product pages was not displaying correctly in all languages using Shopkit of Kadence and WPML. Specifically, in two of the four languages, the images were covering the 'add to cart' button, indicating that styles were not being copied across all languages. Solution: We identified that the problem was due to a translated string in the
admin_texts_kt_woo_extras
text domain. We resolved the issue by deleting its translation, which corrected the gallery display across all languages. To avoid similar issues in the future, when translating strings, it is crucial to copy the entire English string and translate only the necessary parts, such as "Add to Bag."
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. If problems persist, please open a new support ticket.
Problem: The client was experiencing issues with their website after re-enabling Redis. The primary problems included an htaccess error causing a 500 error on the German version of the site and issues with product tags where French tags were being overwritten by English ones. The client was concerned about compatibility issues between WPML and persistent object cache, especially after updating to WordPress 6.7. Solution: We acknowledged that the htaccess issue is known and provided a workaround, which can be found here: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/. For the product tags issue, we suggested that it might be related to the recent update to WordPress 6.7. We recommended creating a staging site and downgrading WordPress to its previous version to see if that resolves the issue. If the problem persists, we advised waiting for the next WordPress update or contacting us for further investigation.
Please note that the solution provided 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 at WPML support forum.
If this solution does not resolve your issue or seems outdated, please check our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client was experiencing issues with WooCommerce taxonomies not being translated in the URL when using WPML with the Kadence theme, resulting in incorrect URLs.
Solution: We recommended updating the WPML plugins to the latest versions, specifically WPML 4.6.10 and String Translation 3.2.10. After updating, the client should edit the product in the default language, make a small change to the content, save it, and then update the translation. This process should ensure that product tabs and attributes display the correct translations.
If you're experiencing a similar issue, we recommend trying the steps mentioned above. However, please note that the solution might be irrelevant if it's outdated or not applicable to your case. If the problem 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. Should you need further assistance, please do not hesitate to open a new support ticket on our support forum.
