Problem: The client has products with variations in one language, but the variable product in the secondary language shows no variations. Solution: We recommend updating WooCommerce Multilingual & Multicurrency to version 5.5.5. You can download the latest versions from your account on My Account → Downloads on wpml.org. For instructions on updating, please visit http://wpml.org/faq/install-wpml/. If you don’t see the update in your dashboard, go to Plugins → Add New → Commercial tab and click “Check for updates”. If the issue persists after the update, please provide step-by-step screenshots showing how you add the attributes and how you translate them. Before proceeding, ensure to back up your database.
This solution might be 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 problem persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing an error on your website where you cannot switch the domain, and the WPML plugin does not work correctly or update. Solution: We recommend re-registering your website. Please follow these steps: 1. Visit https://wpml.org/account/sites and remove your website from the list. 2. Add it again and copy the newly generated key. 3. In your website's admin panel, go to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". 4. Register the website again using the key you copied in step #2.
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: The client reported that the titles of different filter items on their website were not appearing as strings available for translation when using the YITH filters. Solution: We reviewed the issue and found that the YITH filters were translated correctly as per the documentation. The problem was with the widget settings in Appearance > Widgets, where the BG filter widget was set to display on all languages. We adjusted the settings so that the BG filter is shown only on the BG language, and the EN filter is shown only on the EN language. After this change, the filter titles appeared correctly and were available for translation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that even though Woo translations for regions and countries are downloaded, they are not displayed in dropdowns in checkout and settings > Woo > Delivery zones. The Bulgarian strings are displayed instead. Additionally, the filter titles are not visible as strings. Solution: We advised the client to check the language settings of the affected strings in WPML > String Translation. It appears that the strings were assigned to the wrong language. We recommended changing the language of these strings and verifying that the translations are correct. This adjustment should resolve the issue, and the correct translations should then appear on the frontend.
If the problem persists or if this solution becomes 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 these steps do not resolve the issue, please open a new support ticket.
Problem: The client is facing issues with unique translation IDs not connecting the English translations to the original Bulgarian content during imports, despite both languages having matching translation IDs. Solution: We recommended the client to create a test Excel file containing one product in both Bulgarian and English. This will allow us to record a video demonstrating the entire process and identify where the issue might be occurring.
If this solution does not resolve the 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 unable to find and translate the currency symbol 'лв.' in Bookly forms on their website. Solution: We have confirmed with Bookly that currently, currency symbols in Bookly cannot be translated via WPML. They are aware of this limitation and are considering it for future updates. Since this is a limitation on Bookly's side, we recommend monitoring any updates from them regarding this issue.
If this solution becomes irrelevant due to updates or if it does not apply 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After syncing strings in WPML, most translations are not visible on the website, although they are still translated in WPML. This issue is not related to cache problems. Solution: We recommend enabling WP DEBUG to check for any current errors that might be affecting the visibility of translations. You can enable WP DEBUG by following the instructions here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ Look for errors such as "Notice: Function _load_textdomain_just_in_time was called incorrectly." If you find such errors, please provide us with the details. If you are unsure how to use WP DEBUG, please let us know, and we will assist you further.
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, we encourage you to open a new support ticket for personalized assistance at WPML support forum.
Problem: The client is trying to make text on their website translatable using WPML. Specifically, they are working on translating text within a DIVI page and Bookly forms. The issues include text within a tab on a DIVI page not being translatable and the currency symbol 'лв.' in Bookly forms not being found for translation. Solution: The issue with the DIVI page tab not being translatable was resolved by following the documentation on translating pages with the global module.
If the provided solutions do not resolve your issues or if they seem 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 these steps not help, please do not hesitate to open a new support ticket for further assistance.
