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.
