Problem: If you're experiencing issues where prices change incorrectly when the String Translation plugin is enabled, it might be due to custom code in your theme. Specifically, the issue arises from a line in the child theme's
functions.php
file that incorrectly replaces text related to price display. Solution: We recommend checking the
functions.php
file in your child theme, specifically around line 51. Look for the following line of code:
To resolve the issue, you can either comment out or remove this line. This change should correct the price display by preventing the alteration of admin string names that affect how prices are shown.
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 problem persists, please open a new support ticket.
Problem: You are using the xstore theme and want to translate the 'Description after content' field in WooCommerce categories, but only the 'Description' appears after translation. Solution: The field you are trying to translate is a custom term meta. Here’s what you should do: 1. Navigate to WPML > Settings > Custom Term Meta Translation. 2. Change the translation preference for _et_second_description from 'Don't translate' to 'Translate'. 3. You can now translate this second description while translating your categories in WPML > Taxonomy Translation.
If this solution does not resolve your issue or seems outdated, we 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 installed the "Give PW" plugin and used WPML to translate its strings. Although all strings were found and translated, half of them are not appearing translated on the frontend.
Solution: We discovered that some strings originate from JavaScript files like
or TypeScript files, which WPML cannot translate. Additionally, some strings such as "Payment Amount" appear in the String Translation but are sourced from different parts of the plugin, leading to confusion as they are not used in the form itself. To resolve this, the client should refer to the plugin's documentation for translating strings or contact the plugin author for more guidance. It's also noted that the Slovenian translations for the plugin on wordpress.org are only 4% complete. The client can contribute to the translations here or use another tool as suggested in the plugin's documentation.
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. If issues persist, please open a new support ticket.
Problem: The client wanted to know if they can compare WPML AI translations with Google and DeepL, and if WPML AI supports translation to Croatian. Solution: We informed the client that WPML AI currently supports translating content from English to German, Spanish, French, Portuguese, and Italian, but not to Croatian. Regarding the comparison of WPML AI translations with Google and DeepL, we explained that a direct comparison isn't possible. However, the client can toggle the translation engines on and off and translate the content as described in this documentation. It's important to note that translating the same content will not be included in the comparison, as it is stored in the translation memory. More details can be found here: documentation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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 WPML support forum.
Problem: The client was facing an issue where despite translating everything in string translations, the cart was not translated. Additionally, a new cart page with the URL '/cart-2/' was automatically being created and set as the default, which was happening on multiple websites using WPML. Solution: We recommended checking if the 'Auto-generate from title' option was enabled in WPML>>Settings>>Translated documents options>>Page URL settings, as WPML follows WordPress guidelines for creating post slugs. If a post slug 'cart' exists, WordPress will automatically add 'cart-2' for a new post with the same slug. For more details, refer to the documentation on translating page and post URL slugs at https://wpml.org/documentation/getting-started-guide/translating-page-slugs/#translate-page-and-post-url-slugs and https://crocoblock.com/knowledge-base/articles/how-to-create-wordpress-slugs-and-permalinks/.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with listings not being displayed correctly across different language versions of their site. Specifically, listings created in the default language (Slovenian) were not automatically appearing on the English version of the site, and vice versa.
Solution: 1. We ensured that the default language for listings was set to Slovenian, which is the primary language of the site. This allows the 'Translatable - use translation if available or fallback to default language' option to function properly.
2. We clarified that the fallback option only works with the primary language, so listings must be created in Slovenian to be automatically translated to English.
3. For listings created in English, which is a secondary language, we recommended manually translating them to Slovenian to ensure they appear on the Slovenian page.
4. We performed a resynchronization of the listings to correct any out-of-sync issues, ensuring that the listings now display correctly on both language versions of the site.
If you're experiencing similar issues, we recommend checking that your listings are set to the default language of your site and manually translating any listings that were created in a secondary language. If you require custom programming work for more complex translation issues, consider contacting one of our certified partners.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking 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.
Problem: The client was experiencing an issue where clicking on the English flag to switch languages redirected to an incorrect URL, changing '/listing/' to '/product/', which resulted in an incorrect page layout. Additionally, there was a problem with listings not being displayed in both languages. Solution: 1. We identified that some translated strings were breaking the URL slug. 2. We removed the problematic translated strings from the WPML String Translation. 3. We advised the client that if they wish to translate URL slugs, they should do so in WPML > Settings > Custom Post Type Translations, not in the string translations. 4. We split the ticket to address the issue of listings not displaying in both languages, which can be followed up here.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we recommend opening 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. If further assistance is needed, please contact us in the WPML support forum.
Problem: The client was trying to translate a homepage but found that only the page title was showing in the translation. The content was mostly displayed from listings and categories, which had not been translated. Additionally, the client was using a custom Elementor widget from the Listeo theme and was unsure how to enable translation for it.
2. To display listings in both languages without translating them, we advised enabling the 'Translatable - use translation if available or fallback to default language' option. This allows listings to be shown in all languages, displaying the content from the primary language if no translation is available.
3. If automatic translations are not desired, the client can turn off this feature. With the 'Translatable - use translation if available or fallback to default language' option selected, translated pages will still display listings from the primary language.
If the solution provided here 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 you still need assistance, please open a new support ticket with us: https://wpml.org/forums/forum/english-support/
