Problem: If you're experiencing an issue where the Fibo Search block is not showing in the translated version of your menu, despite being added correctly via Appearance > Menus in the secondary version. Solution: We recommend checking the settings at Appearance > Menus on the translated menu. Ensure that you set the Layout for the FiboSearch bar to "Search bar". This adjustment resolved the issue in our local tests.
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.
Problem: Text in some checkout fields regarding shipping options and payment options are not translated. Solution: If you're experiencing untranslated text in checkout fields, we recommend you first change the language of the current strings to Latvian and then translate them to English to see if this resolves the issue. Additionally, you can change the source language of the whole domain for current and future strings via WPML->String Translations->Set the original language of themes and plugins. For further assistance, please provide us with your debug information by following the detailed instructions at http://wpml.org/faq/provide-debug-information-faster-support/.
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, do not hesitate to open a new support ticket at WPML support forum.
Problem: You need to change the URL translation for WooCommerce products. Solution: We recommend enabling the translation of the product slug by adjusting your WPML settings. Here’s how you can do it: 1. Navigate to WPML → Settings → Translated documents options and select the “Translate” option. This setting allows the slug to be translated manually. 2. If you are working with an existing product and its translation, trigger an update to make the slug appear in the Translation Editor by: a. Making a small change to the product description in the original language. b. Updating the product. c. Opening the Translation Editor for the translated product. After these steps, the slug field should be available for manual translation in the Translation Editor.
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 at WPML support forum.
The client was experiencing issues with ACF fields not being translated in their products, displayed in white boxes within an Elementor Loop Grid. In the English version, these fields appeared as empty spaces. Additionally, the links within these fields did not translate correctly and targeted the original language URLs instead of the translated ones.
Solution:
We advised the client to set the 'acf_field_group' CPT to 'Not translated' in WPML > Settings > Post Types Translation, as having it set to 'translated' is not recommended. This change required re-translating the products where the ACF fields were missing.
For the links in the Elementor template, we identified a bug where the 'URL' field set to 'copy' by default was not being automatically converted.
As a temporary workaround, we suggested switching the field group to the 'Expert' mode and setting the 'URL' field translation preference to 'Translate'.
After updating the original post, the 'URL' field will appear in the translation job, allowing to manually convert the URL.
Problem: If you're experiencing issues with changes not appearing on your site after modifying colors, such as the Active Language link not being darker as expected. Solution: We recommend using custom CSS to achieve the desired visual changes. For instance, to darken the background color of the current language in the WPML language switcher, you can add the following CSS code:
You can insert this CSS in WPML → Languages → Language switcher options → Additional CSS.
Please note that this solution might be irrelevant if it's 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 at WPML support forum.
Problem: If you're experiencing 404 errors on product category pages after activating WPML, it might be due to incorrect translation settings. Solution: We recommend checking the translation of your product categories in WPML. Specifically, ensure that the product category slug is correctly translated to match the original language setting. You can do this by navigating to WPML → String Translation and verifying that the 'product-category' is translated appropriately. If it's not, update the translation accordingly.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, we highly recommend opening a new support ticket. Additionally, please 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, you can also visit our support forum at https://wpml.org/forums/.
Problem: The client needed to know how to find the word count for their site using WPML and also inquired about editing translations globally after using AI translation, specifically for handling incorrectly translated terms. Solution: We advised the client that when they are on the Translation Dashboard and select a page, they can see at the bottom the number of words that need to be translated, how many credits are used, and the exact price. Unfortunately, an estimate for the entire website is not currently available, but the client can check the estimated cost for each selected page or post.
For editing translations globally, we recommended that from WPML > Settings, the client can choose to review the translation or set specific terms and their translations in the Glossary, which will then be used in automatic translations. More details on managing glossary entries can be found here: How to Create and Manage Glossary Entries.
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.
