Problem: The client was unable to see the 'Woo Filter by Price' element on the English and German pages of their Avada theme, preventing duplication and translation. Solution: We identified that the 'Woo Filter by Price' element might not automatically duplicate or translate due to its dependency on WooCommerce widget areas or filter logic. Here are the steps we recommend: 1. Ensure the element exists in the original layout and check if it's set to appear based on widget areas or dynamic conditions that might differ on translated pages. 2. If the element is added via a widget, go to Appearance > Widgets and verify if it's present in the language-specific widget areas. 3. If necessary, manually recreate the filter for each translated language. 4. Ensure that all products and categories you wish to filter by are translated into the respective languages. 5. Navigate to the backend of the German version of the Shop template, select 'Edit anyway', and manually add the missing price filter. 6. Use the WordPress editor as recommended by Avada developers for translating layout sections. More details can be found here: Translating Avada Layout Sections.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where product variations such as color and size are not included in the
line_items.name
attribute in the WooCommerce REST API response when the 'WPML Multilingual & Multicurrency for WooCommerce' plugin is active.
Solution: 1. Verify product attribute translation settings through the WooCommerce Multilingual attributes tab. 2. Synchronize product variations using WPML troubleshooting tools and re-save the variable product. 3. Check how variations are displayed in the backend order details in WooCommerce admin and verify the order language. 4. Use the
?lang=nl
parameter in the REST API call. 5. If these steps do not resolve the issue, reproduce the API request on a staging site with the same plugin/theme setup to confirm if there is a compatibility or integration issue between WPML and WooCommerce REST API for variable products. 6. Examine any filters or overrides on the REST API response, particularly those added by WPML or the theme.
If the problem persists, we 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 solution provided here is outdated or not applicable to your case, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where some WooCommerce checkout strings, such as 'Населённый пункт' and 'Saadetis', are not using the translations set in WPML → String Translation in both Estonian and Russian languages, despite having disabled automatic updates and cleared caches. Solution: We recommend exporting the .pot file with the updated strings from a test site where the issue is already resolved. You can do this via WPML → String Translation → Import/Export → Export strings. Then, import this .pot file into your live site using the same WPML → String Translation → Import/Export path. This process is safe to perform on a production site and should not affect your existing content or database structure. Additionally, this fix should remain effective after future WPML or WooCommerce updates, although you may need to re-scan for new strings or re-export/re-import the .pot file if updates introduce changes.
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 at WPML support forum.
Problem: Se stai cercando di gestire la traduzione multilingua di prodotti variabili con WooCommerce Product Add-ons e incontri problemi con la sincronizzazione e collegamento dei dati dopo la creazione o importazione delle versioni linguistiche, potresti riscontrare due problemi principali: 1. Le immagini delle variazioni non sono correttamente associate alle rispettive variazioni in inglese, e il campo
_thumbnail_id
non è visibile nelle impostazioni di traduzione dei campi personalizzati. 2. Le opzioni dei campi Add-on di tipo Dropdown non vengono copiate correttamente.
Solution: Per risolvere questi problemi, ti consigliamo di seguire la documentazione ufficiale fornita dallo sviluppatore di WAPF, che suggerisce di utilizzare la traduzione manuale (Editor WordPress) invece dell'Editor di Traduzione Avanzato (ATE) per evitare problemi con i JSON complessi e la logica condizionale. Puoi trovare la guida qui: https://www.studiowombat.com/knowledge-base/how-to-translate-fields-with-wpml/
Se questa soluzione non dovesse essere più rilevante, perché potrebbe essere superata o non adatta al tuo caso specifico, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare i problemi noti su https://wpml.org/known-issues/, verificare la versione della correzione permanente e confermare che hai installato le ultime versioni di temi e plugin.
Problem: The client is facing an issue where a checkbox is not appearing at checkout in Greek on their WooCommerce site, although it appears in English. Solution: We have identified that the issue is not caused by WPML. The problem arises because WooCommerce blocks rely on JavaScript translation files (.json files), which are not fully supported by WPML String Translation. Consequently, the site loads the native WooCommerce translations. In this case, the Greek translation for that string is incomplete. To address this, you can contribute to completing the translation at WordPress translation project.
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 WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem: The client is unable to translate certain texts on the WooCommerce block-based checkout page, specifically in the coupons section, tax text, and terms and conditions consent text. The client has tried various methods within WPML to locate these texts for translation but has been unsuccessful. Solution: We recommend replacing the block-based Cart and Checkout pages with their shortcode equivalents to resolve this issue. Use the following shortcodes:
[woocommerce_cart]
[woocommerce_checkout]
After implementing these shortcodes, the missing texts should become available for translation in WPML → String Translation. If any strings still don’t appear, you can scan the theme and WooCommerce via WPML > Theme and plugin localization and then translate them in WPML → String Translation. For more details, visit https://wpml.org/errata/woocommerce-multilingual-cart-page-strings-not-translated-when-using-blocks/.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client is experiencing a persistent warning in the WordPress admin indicating that the 'product_type' field was set incorrectly for some product translations. This issue persists despite following standard troubleshooting procedures, including using the fix button on the WooCommerce Multilingual & Multicurrency troubleshooting page, confirming taxonomy settings, clearing caches, running WPML troubleshooting tools, and conducting a plugin conflict test. Solution: We recommend trying the workaround provided in this support forum thread. If the warning continues, we suggest providing temporary access (WP-Admin and FTP Login info) to your site, preferably a staging site, so we can further investigate and debug the issue. Before proceeding, please ensure you back up your database and website. We will need your permission to deactivate and reactivate plugins and the theme, and to change configurations on your site.
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 experiencing an issue where English product URLs in WooCommerce, which should use '/our-products/', are redirecting to the Swedish version '/vara-produkter/'. Despite setting the correct slugs in WooCommerce Multilingual, the redirection persists. Solution: 1. Enable Slug Translation in WPML Settings: Ensure that WPML is set to translate custom post type slugs by navigating to WPML → Settings, finding the Slug translations section, and enabling the option Translate base slugs of custom post types and taxonomies (via WPML → Taxonomy translation). Save any changes made. 2. Configure Product Base Slugs in WooCommerce Multilingual: Set the specific product base for each language by going to WooCommerce → WooCommerce Multilingual & Multicurrency, clicking on the Store URLs tab, and ensuring the English Product base is 'our-products' and the Swedish is 'vara-produkter'. Save each language setting. 3. Flush Permalinks: Refresh WordPress's permalink structure by navigating to Settings → Permalinks and clicking the Save Changes button. 4. Check and Translate Product Base Slugs in String Translation: Go to WPML → String Translation, search for 'our-products' and ensure its translation for English is correct. Repeat for 'vara-produkter' in Swedish. Save any changes. 5. Clear Caching: Clear any site or server-level caches to ensure changes are reflected on the frontend.
If these steps do not resolve the issue, it may be necessary to further investigate the settings or consider other conflicts. If the problem persists or the solution seems outdated, we 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 open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the credit card form on the checkout page does not appear correctly in the default language, although it appears fine in the sublanguage. The client questioned if WPML might be conflicting with any plugins. Solution: We have investigated the issue and determined that it is not related to WPML. It seems to be linked to the server environment or the payment methods used. We recommend the following steps to diagnose the issue further: 1. Temporarily deactivate all WPML plugins. 2. Ensure that your WordPress site language is set to English. 3. Visit the checkout page (/checkout/). 4. Check if the credit card form issue persists. If the form appears correctly with WPML plugins disabled, it should also work correctly once you reactivate WPML.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 needed, do not hesitate to open a new support ticket for further assistance.
Problem: You are experiencing a 404 error when trying to access any of the sites. The links appear correct, but the pages do not display. However, when changing the language in the table view of the templates and pressing the view button, everything shows as translated with the sample data, but it does not work with the real data on the live site. Solution: If you're encountering this issue, we recommend you try the following steps: 1. Go to WPML → String Translation. 2. Search for both 'product-category' and 'Kategori', then delete all related entries that appear. 3. Go to Settings → Permalinks and click Save Changes to refresh them. 4. Navigate to WooCommerce → WooCommerce Multilingual & Multicurrency → Store URLs and retranslate the product category. Please ensure to take a full site backup before proceeding.
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.
