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.
Problem: The client is experiencing issues with excessive scheduled actions in the WooCommerce 'wp_actionscheduler_actions' table when deleting translations of products in English, which were not removed when the original product in Spanish was deleted. This causes the database to exceed the limit of their hosting plan. Solution: We recommended clearing the cache and deactivating non-essential plugins before attempting to delete products to ensure the site has more resources available. Additionally, we suggested increasing the 'max_input_vars' limit from 3000 to 10000 with the hosting provider. For a more controlled environment, we created a staging site and discovered that the issue stems from a missing 'priority' column in the 'wp_actionscheduler_actions' table. The temporary fix involves running the following SQL command:
ALTER TABLE wp_actionscheduler_actions ADD COLUMN `priority` int(20) NOT NULL DEFAULT 10 AFTER `group_id`;
However, this is a temporary solution, and the client should seek a permanent fix from WooCommerce support.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client reported losing all content created with Bricks PageBuilder and encountering issues with endpoints switching to English and adding unwanted suffixes in a multilingual WooCommerce setup. The default language was set to Dutch, but endpoints were incorrectly resetting. Solution: We advised the client to perform a full backup and provided assistance by resetting the WordPress endpoints to their original state and ensuring the default language remained in Dutch. We also recommended translating the endpoints back to the required languages using the String Translation feature of WPML. To address the issue with the URLs, we suggested keeping the English endpoints on the WooCommerce settings page and translating them as needed. We also resolved an issue where the Dutch default was missing the '/nl' URL part by reactivating the directory option for URLs.
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.
Problem: If you're experiencing issues with product listings showing a grey box on the second page of results in a secondary language (Dutch) on your website, even after clearing server and WPML caches, we have identified a solution. Solution: We recommend editing the product in the original (English) language and simply clicking on 'Update'. This action can be performed in bulk on the product listings page to address the issue for all affected products. Please try this on your staging site first to confirm that it resolves the issue.
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 the problem persist, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client reported that their stock is reduced multiple times when an order is processed, observing multiple stock reduction messages in both the original and translated languages. Despite using troubleshooting tools and clearing caches, the issue persisted. Solution: We suggested the client to: 1. Temporarily disable all WPML plugins. 2. Place a new order using the same product as in the problematic order. 3. Check if the same stock reduction issue occurs. This test will help determine if the issue is related to WPML or another factor. If the problem persists even with WPML disabled, it confirms that WPML is not causing the issue. We also recommended testing with only WPML, WooCommerce Multilingual (WCML), and WooCommerce activated, while all other plugins are temporarily disabled, to rule out conflicts with third-party plugins.
The client found that the issue was caused by too many webhooks configured in the payment gateway.
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, 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.
