Problem: The client is unable to translate the components of the 'Thank you' page in WooCommerce using the NextMove plugin into other languages. Despite following outdated documentation and attempting translations through String Translation and direct page translation, the components still appear in the original language, Russian. Solution: We recommend the following steps to resolve the issue: 1. Ensure each translation of the 'Thank you' page uses a unique slug. 2. After setting the unique slugs, re-save the permalinks for each language you are translating. This action should help the components of the page to display correctly in the intended language.
If these steps do not resolve the issue, or if the 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 problems persist, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with database corruption or sync failures affecting the functionality of automatic translation services. Specific problems include a sidebar widget only displaying the 'Uncategorized' category in English, a main menu not displaying correctly in English compared to Greek, and a product brands display issue where a widget on an Elementor page shows only 3 out of many translated brands. Solution: For the menu synchronization issue, we adjusted the custom field settings for the menu to 'Don't translate' in WPML → Settings → Custom Fields (make sure to enable Show system fields). After this adjustment, we resynchronized the menu, which resolved the display issues. We also provided a video explaining these steps, which can be viewed here: https://kommodo.ai/recordings/mSRwHSpl4zMg9G75t8W8.
If this solution does not resolve your issue or 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 https://wpml.org/forums/forum/english-support/.
Problem: The client reported extreme performance issues with their WooCommerce site when WPML Multilingual CMS and WPML String Translation were enabled, causing page load times to exceed 2 minutes. The slowdown was suspected to be due to heavy database queries or translation-related overhead.
Solution: We identified that the AJAX request for WooCommerce Fragments (get_refreshed_fragments) was causing longer load times, as every fragment passed through translation filters. A known bug in WCML caused fragments to refresh multiple times unnecessarily. We suggested a workaround to disable cart fragments if an auto-updating mini-cart was not needed, using the following code:
Additionally, we found that the first uncached page load was extremely slow regardless of WPML being active, indicating a potential issue with the caching setup. We implemented the above workaround in the Child Theme, which improved the load time to about 6 seconds with WPML enabled.
We also recommended ensuring that the WPML Multilingual & Multicurrency for WooCommerce addon was enabled and that WPML and its addons were updated.
If you're experiencing similar issues, we recommend trying the provided workaround and checking your caching setup. It's also important to ensure that all WPML components are up to date. If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please visit our support forum at WPML Support Forum and 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.
Problem: The client was unsure whether to change the taxonomy translations from English, similar to concerns with WooCommerce endpoints, and needed clarification on setting up and managing taxonomy translations in WPML.
Solution: We reassured the client that translating taxonomies in WPML is a supported process and provided a detailed guide on how to properly set up and manage these translations:
1. Check Taxonomy Translation Settings: * Navigate to WPML → Settings in the WordPress admin. * Scroll to the Taxonomies Translation section. * Ensure the taxonomy is set to Translatable – only show translated items.
2. Translate Taxonomy Terms: * Translate terms via WPML → Translation Dashboard or directly at WPML → Taxonomy Translation.
3. Translate Taxonomy Base Slugs: * This can be done in the Taxonomies Translation section under WPML → Settings, where you can set different slugs for different languages.
We also addressed a specific issue where English was set as the original language for category taxonomies, explaining that WPML treats the language of initial term creation as the original. We guided the client to check and correct the language connections if they were set incorrectly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly 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 Danish and English attributes for WooCommerce are switched for some attributes and not for others. Solution: If you're experiencing this issue, we recommend you go to WPML-> Taxonomy Translation, select the product attributes, and ensure that they are in the correct language.
Please note that 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: WPML Media Translation marked as 'Not Installed' on the Support page. Solution: We resolved this issue in the latest version of WPML (4.9.0). To address this, please follow these steps: 1. Go to your site’s admin area. 2. Navigate to Plugins → Add New Plugin and select the Commercial tab. 3. Click the 'Check for updates' button. 4. Find WPML 4.9 in the list and click 'Install'. Before proceeding, ensure you make a full site backup (files and DB). For more details on WPML 4.9.0, visit this link.
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 issues persist, please open a new support ticket.
Problem: WCML - Default Form Value is not selected if the attributes were created in the scondery language. Solution: We recommend updating to the latest version of WCML (5.5.4), along with WPML (4.9.0) and Strings Translation (3.5.0). Before updating, ensure to back up your site fully, including files and the database. You can check for updates by visiting your-domain.com/wp-admin/plugin-install.php?tab=commercialyour plugin installation page and clicking the 'Check for updates' button.
If this solution does not apply to your case because it might be outdated, or if you encounter further issues, 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. Please feel free to open a new support ticket with us for additional assistance.
Problem: The client is experiencing an issue where no shipping options are available for Dutch language checkout in WooCommerce, using WPML and the plugin 'Advanced Shipping Rates for WooCommerce'. This problem arose after recent updates to WPML, WooCommerce Multilingual, and WooCommerce, even though the shipping configurations have not changed. Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Ensure that each shipping class has a Dutch translation assigned in WPML. Navigate to WPML → Taxonomy Translation → Shipping Classes. 2. Check for any configuration issues in WooCommerce by going to WooCommerce > WCML > Status. 3. Verify that the Dutch product has the correct shipping class set in the WordPress Editor. If necessary, edit the original product and update its translations using the WPML Translation Editor. If these steps do not resolve the issue, consider simplifying the shipping setup to be based on cart totals instead of shipping classes, as the client chose to do.
Please note that this solution might be outdated or not applicable to your specific case. If the issue 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 at WPML support forum.
Problem: The client is experiencing issues with tax calculations and currency conversions in their multilingual and multicurrency setup using WPML. The problems are specifically occurring with Google feeds and in the accounting system where taxes and currency values are incorrect for orders in languages other than the main one. Solution: We recommended the client to install a specific plugin on a test site to help diagnose the issue. We provided a link to the test site and asked the client to notify us once the plugin installation is complete. This step is crucial to replicate and understand the problem better.
If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: Il cliente ha riscontrato due problemi critici nel sito multilingue: 1. Le variazioni WooCommerce non appaiono nella versione spagnola del sito. 2. I campi personalizzati del plugin Advanced Product Fields for WooCommerce non sono traducibili in WPML. Solution: Per il primo problema, abbiamo suggerito di verificare che i prezzi siano sincronizzati e di utilizzare gli strumenti di "Risoluzione dei problemi" in WooCommerce Multilingual per sincronizzare le variazioni e rigenerare le tabelle di ricerca. Per il secondo problema, abbiamo identificato che il campo _wapf_fieldgroup può essere impostato su 'Copy' per copiare il gruppo di campi nel prodotto tradotto. Tuttavia, i label, le istruzioni e i placeholder dei campi non possono essere tradotti con WPML a causa della loro struttura interna serializzata.
Se questa soluzione non risolve il tuo problema o sembra non essere più attuale, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare le questioni note e di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: Wenn WooCommerce Multilingual & Multicurrency (WPML) aktiv ist, werden Transaktions-E-Mails für Buchungen, speziell 'Neue Buchung' und 'Bestätigung ausstehend', doppelt versendet. Dies tritt nicht auf, wenn WPML deaktiviert ist. Solution: Der Konflikt liegt in der Datei
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme und stellen Sie sicher, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
