Problem: The client wants to set a specific product with a different currency and have other currencies converted from this set currency on a multi-vendor platform using Dokan. The client also inquires if it's possible to set a different main currency for each vendor. Solution: We informed the client that currently, WooCommerce Multilingual or WooCommerce does not support setting a specific currency for a vendor, user, or country. However, a future version of WooCommerce Multilingual (5.5) will include a feature to set prices based on the country, but it is still in the early development stage. For now, a custom plugin might be necessary. We suggested checking out the WooCommerce Product Price Based on Countries plugin, although we have not tested this ourselves. For custom development, we recommended contacting certified developers through this link. Additionally, we provided a code snippet using the
wcml_raw_price_amount
hook to convert from the WooCommerce default currency price to another currency, and pointed to the function that auto-updates product prices in other currencies:
The update_exchange_rates function is defined in the *wp-content/plugins/woocommerce-multilingual/classes/multi-currency/class-wcml-exchange-rates.php* file (line 151).
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 further assistance is needed, please open a new support ticket at WPML support forum.
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 further assistance is needed, please open a new support ticket at our support forum.
Problem: The client created a custom Elementor widget containing an image, headline, and text, and encountered an issue where the image did not change when switching languages, despite using WPML's Media Translation. Solution: We recommended the following steps to resolve the issue: 1. Ensure that the image within the custom Elementor widget is stored as a URL and that the URL field is registered for translation in the XML configuration. 2. Make a small update to the source page and save the changes. 3. Update the translation and use the Advanced Translation Editor to search for the image URL. If found, replace the URL with the correct image URL for the desired language. 4. If the URL does not appear in the translation editor, it's possible that the widget and its configuration need further adjustments. We suggested replicating the issue in a WPML sandbox environment to further diagnose the problem. 5. If manual translation of the image URL is required, consider integrating the Elementor widget with WPML Media Translation using a custom integration class, which may require hiring a developer proficient in WPML.
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.
Problem: The client is unable to send categories and tags to translators using WPML, and documents are not showing up on the translated site. Additionally, titles and notices were not included in the xliff file and thus not translated. Solution: To address the issue of translating categories and tags, we recommend translating the Categories and Tags taxonomy terms manually from WPML>>Taxonomy Translation. Alternatively, create a private post including all the Categories and Tags taxonomy terms, and send that post for translation. For detailed guidance, please refer to our documentation on translating taxonomy terms from a central page and how to translate all taxonomy terms at once.
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.
Problem: The client needed to modify the hreflang links for dynamic pages that exist only in the main language (FR) and wanted to know if there is a hook to filter or remove these links. Solution: We recommended using the
wpml_hreflangs
hook to change or remove the alternate hreflang links. We provided examples of how to implement this filter with links to relevant documentation:
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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 contact us directly at WPML support forum.
Problem: If you're checking the translation for the Post "Mand" and notice that the link field is missing in a custom Gutenberg block inside a custom field, this might be due to the way links are handled. Solution: We recommend you first make a full backup of your website. Then, you need to modify the PHP code that registers the strings for ACF blocks. Specifically, edit the file
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.