Problem: You are using WPML with Elementor Pro, WooCommerce, and Bookings for WooCommerce on your website and are trying to translate a single booking product page. However, the date picker is not visible on the translated page, which prevents service purchases. Solution: We have identified that this issue has been resolved in the latest versions of the Bookings for WooCommerce plugin. The plugin's author has included a fix in the recent update. Here are the details from the plugin's change log:
3.10.1 – Released on 28 November 2025<br />New: Latest compatibility With WP[6.8.3] and WC[10.3.5].<br />New: Compatibility with WPML
We recommend updating the Bookings for WooCommerce plugin to the latest version to resolve this issue.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open 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: You are using the Real Homes theme and have created a search form with Elementor. Although you have translated the Property Features taxonomies using WPML, the translated features are not displaying in the Elementor search form, except for one feature that remains untranslated and in English. Solution: We tested the issue by setting up a new test site with the Real Homes theme and its plugins. After translating a property and its taxonomies, we added the "RH: Search Form 2" widget on a translated page. The form displayed all features correctly in the translated language. It appears that the "RH: Search Form 2" widget does allow using Real Homes Templates, which are set up in the Customizer's search settings. If you use such a template, you might run into unexpected issues. We were sadly not able to replicate and investigate this issue, as we would require a license key for Real Homes for this purpose. We recommend using the widget without any templates, in case you run into unexpected issues.
If this solution does not resolve your issue or seems outdated, we recommend checking the related 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.
Problem: The client is experiencing issues with the 'YITH WooCommerce Dynamic Pricing & Discounts Premium' plugin when using the multicurrency feature of WPML. Specifically, the free gift popup does not add the product with the correct price in different currencies, and sometimes the product is not added to the cart at all. Solution: UPDATE: This issue was solved in YITH WooCommerce Dynamic Pricing & Discounts Premium 4.26.0.
1. We suggested that the issue might be due to the plugin not recognizing WPML/WCML currencies and offered a WPML test site to replicate and address the issue. 2. We provided a workaround involving a code snippet to be added to the functions.php file of a Child Theme or a Code Snippet plugin. The code snippet is available at https://wpml.org/errata/yith-woocommerce-dynamic-pricing-discounts-premium-gifts-not-added-and-currency-switch-fails-on-ajax-requests/. 3. We recommended saving YITH rules only in the site's default language and checking WPML > String Translation for any incorrectly translated strings that might affect functionality.
If this solution does not resolve your issue or seems outdated, we 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/forum/english-support/.
Problem: The client reported that the Bricks Builder blog template layout was not displaying correctly in translated versions, despite multiple updates to the translation. The issue persisted even after creating separate templates for each language and manually connecting them. Solution: We investigated the issue and found that it was related to the translation settings in WPML. Specifically, the settings under WPML > Settings > Custom Field Translation had been modified. To resolve the issue, we recommend: 1. Reverting the translation settings to match those on our sandbox site. 2. Resaving the original template and its translations. Please ensure to back up your site before making these changes.
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 open a new support ticket.
Problem: The client is using LightspeedHQ to manage stocks between their physical store and WooCommerce webshop, which has been translated into English and German using WPML. They noticed that orders placed on the translated versions of the site are not being synced to the LightspeedHQ system. This issue arises because WPML creates duplicates of products for each translation, each with different product IDs, which LightspeedHQ does not support. Solution: We suggested verifying the REST API responses from the client's website to ensure they are correct and can be retrieved properly in both languages. We recommended exploring the use of a dedicated plugin that supports WPML and can handle translated products. Two potential plugins to consider are:
If these plugins do not resolve the issue, we advised checking with the plugin authors to confirm whether their solutions support the needed functionality and how they process the data. Additionally, we confirmed that WPML's behavior of creating new product IDs for translations is standard and cannot be adjusted.
If this solution does not apply or is outdated, we recommend opening a new support ticket. We also highly suggest 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 experiencing issues where the CSS breaks on translated pages of your website, it might be related to how global sections are rendered within your theme. Specifically, the Code Snippets plugin may not be loading your theme's CSS correctly for the second language. Solution: We recommend using a Child Theme instead of the Code Snippets plugin. You can add the following snippet to the functions.php file of your Child Theme to address some of the CSS issues:
add_action('init', function() {
// Hook location to output the global section
$location_hook = 'nectar_hook_global_section_footer';
add_action($location_hook, function() use ($location_hook) {
// Detect current language
$current_lang = apply_filters( 'wpml_current_language', null );
// Default section ID (Spanish)
$global_section_id = '24759-2';
// Use translated section ID for English
if ( $current_lang === 'en' ) {
$global_section_id = '26378';
}
// Default category ID (Spanish)
$category_id = 47;
// Use translated category ID for English
if ( $current_lang === 'en' ) {
$category_id = 156;
}
// Output the section only if we're on the correct category archive
if ( is_product_category( $category_id ) ) {
Nectar_Global_Sections_Render::get_instance()->output_global_section($global_section_id, $location_hook);
}
});
});
However, if disabling the Code Snippets plugin resolves all issues, we suggest not using it and instead managing code through the Child Theme as shown above.
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.
