Problem: If you're experiencing issues with currency switching on your site when not logged in, and your site uses WCML without WPML, along with multi-currency settings similar to those shown here: https://www.screencast.com/t/hadJtfwc1E, it might be related to WP-Rocket caching. Solution: We recommend following the workaround provided in our errata page for issues with WP-Rocket where currency does not change on the products page. You can find the necessary steps here: https://wpml.org/errata/wp-rocket-currency-not-changing-in-products-page/.
If this solution does not resolve your issue or seems irrelevant due to being 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: The client is working on a site under development using WPML and has encountered an issue where two URLs point to the same product category, but one of them should not be available as it is intended for the English site. Solution: We reviewed the site's configuration in WooCommerce Multilingual and WPML Settings and found no initial misconfigurations. However, we identified that a custom permalink plugin might be altering the permalink settings for categories and archives, potentially causing the issue. We recommend: 1. Disabling the "Custom Permalinks" plugin. 2. Resaving the permalink structure by navigating to Settings > Permalinks on your dashboard. 3. Checking if the issue persists after these changes. If the problem continues, consider setting up a testing site to replicate the issue, allowing us to troubleshoot without affecting your main site.
If this solution does not resolve your issue or seems outdated, 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. We highly recommend opening a new support ticket if needed at WPML support forum.
Problem: If you're trying to install and activate WooCommerce Multilingual & Multicurrency and encounter a PHP Fatal error: Uncaught Error: Call to undefined function icl_register_string(), this issue might be familiar. Solution: We recommend checking your database. Specifically, connect to your database, open the wp_options table, and search for the option_value "_wcml_version". Delete this option from the table. If the problem persists, also delete the entry "_wcml_settings" as it might contain outdated language information not currently used on your site.
If you need further assistance with this fix on your live site, please don't hesitate to contact us. 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 this solution does not resolve your issue or seems irrelevant, please open a new support ticket at WPML support forum.
Problem: You are using pure SQL to duplicate variable products, but the newly created products/variations do not appear in the backend product list or in the product edit page under Product Data => Variations. Solution: If you're experiencing this issue, we recommend using the wpml_set_element_language_details hook to programmatically set the default language for your newly created products/variations. To batch add records into wp_icl_translations for these products, you will need to manage the related information in the icl_translations table. For more details on handling this table, please visit WPML Tables documentation.
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 issue persists, please open a new support ticket.
Problem: The client's site is set to Translate Everything Automatically mode, but a newly created product category did not get automatically translated. Solution: We explained that automatic translation is only possible with the Advanced Translation Editor for specific content types such as posts, pages, templates, and other contents covered by our addons. To translate a product category automatically, the client should edit the original product category and then send a product with this category to automatic translation. Alternatively, creating a draft product, assigning all product categories, and sending it to automatic translation will also translate any product category not yet translated. For more details on translating taxonomies, we recommend reading our documentation here: Translating Post Categories and Custom Taxonomies.
If this solution does not apply to your case, or if it seems outdated, 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. If issues persist, we highly recommend opening a new support ticket for personalized assistance.
Problem: You are developing a site using Elementor with WPML and want to auto-translate links in Elementor icon list items. Despite setting a glossary for the link and resending the page to auto translation, the link remains untranslated. Solution: 1. First, edit the translation of the page. In the Advanced Translation Editor (ATE), use the search option at the top left to find the URL. You can search for the entire URL or just a part of it. For more details, see Translating links with Advanced Translation Editor. 2. If the above step does not resolve the issue, follow these steps: - Go to WPML -> Settings -> Custom XML Configuration tab and paste the following code:
- Press the Save button. - Modify the original page slightly and press the Update button. - Update the translation via WPML's Advanced Translation Editor. - Re-open the translated page to check if the links are now translated.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: If you're trying to manually change the slug of a translated page and are having trouble doing so with your current settings. Solution: We recommend switching your setting to 'Translate'. After making this change, perform a minor edit in the original language to prompt the translation requirement. Then, access the translation editor where you will find the option to translate the slug. For detailed guidance, visit Translating Page Slugs.
Please note that this solution might not apply if it's outdated or not relevant 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 this solution does not resolve your issue, please open a new support ticket.
Problem: If you're experiencing issues where ACF Field Groups are set to 'untranslatable' in WPML -> Settings -> Post Type Translation, but they still appear in the Translation Management post type dropdown filter, this might be confusing. Solution: We would like to clarify that setting the ACF Field Group to 'Not Translatable' in WPML settings means that the entire field group itself cannot be translated using WPML. However, the field labels and placeholders within these groups remain active and translatable. These elements appear in the dropdown to allow you to send field labels and titles for translation through the Translation Management or String Translation, but not the entire field group itself. If you set the field group to 'Translatable', then you can send the entire field group, including all related information and settings, for translation.
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 the problem persists, please feel free to open a new support ticket at WPML support forum for further assistance.
