Problem: The client is experiencing issues with variation thumbnails not displaying correctly on the Croatian (HR) version of their WordPress site, despite working fine on the original Slovenian (SI) version. The client is using the Product Gallery Slider for WooCommerce plugin and has been manually adding each variation for the Croatian language. Solution: We recommend the following steps to ensure that variation images are correctly copied to the translated versions of the products: 1. Navigate to WPML > Settings and locate the Custom Field Translation section. 2. Click on the Show system fields link. 3. Search for the
wavi_value
field in the Custom Field Translation section. 4. If found, set the translation preference for this field to 'Copy'. 5. Save the changes and clear the cache on both your site and browser. 6. Make a minor edit to the product title of a default product and save the changes. 7. Update the translation and check if the issue is resolved.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Sie verwenden WooCommerce mit Germanized Pro und haben eine Rechnungsvorlage auf Deutsch erstellt, die als PDF an Kunden gesendet wird. Wenn Kunden die Webseite auf Englisch besuchen und dort bestellen, erhalten sie dennoch das Rechnungs-PDF auf Deutsch. Solution: Wenn Sie möchten, dass englischsprachige Kunden eine Rechnung auf Englisch erhalten, sollten Sie die Vorlage duplizieren und die Inhalte manuell für die Sekundärsprachen anpassen. Dazu ist es notwendig, den WPML-Editor für die Vorlage zu deaktivieren. Eine Anleitung dazu finden Sie hier: Anleitung zur Deaktivierung.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: The client is trying to use media translation to translate an image on an Elementor page, but the original image still appears on the translated page despite configuring WPML settings for media translation and scanning and replacing media after saving the translated image. Solution: This issue may occur if there was a mass import or a change that did not trigger WPML to detect a change in the original version of the product, which is necessary for image translation. To resolve this, the client needs to make a small change on each product page to prompt WPML to perform the translation. Alternatively, the client can use the bulk edit feature by going to the WordPress Dashboard > Products, selecting the products, and clicking the edit option at the top. Without changing anything, clicking the update/save button will force WPML to recognize the changes and perform the necessary translations. However, this will cause all the products to appear as needing translation completion, indicated by a circle icon, until the translation is verified as 100% complete.
If this solution does not apply or is outdated, or if further issues arise, 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.
Problem: The client is developing a site and needs a separate payment gateway for each currency. The gateway is custom coded, and the client wants to make it compatible with WPML's multicurrency feature. Solution: We recommend setting up your payment gateways in the Payments section of WooCommerce>>Settings, as these should be available for all currencies added via WooCommerce Multilingual Multi Currency features. For more details, please refer to our documentation on multi-currency support in WooCommerce.
Our developers have confirmed that normally any payment gateways configured should be available for all supported currencies. However, our documentation lists only the most common payment methods like WooCommerce PayPal Payments, Stripe, and direct bank transfers.
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: When switching from English to Dutch on the website, the cart content is removed despite the 'synchronize cart content' setting being enabled in WooCommerce Multilingual & Multicurrency. Solution: If you're experiencing this issue, we recommend selecting the option Prompt for a confirmation and reset the cart. This setting helps manage the cart contents when changing languages. Additionally, you can display the list of items cleared from the cart by adding a widget we created for this purpose. For more details, please visit Clearing Cart Contents When Language or Currency Change.
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 at WPML support forum.
Problem: You are trying to translate product reviews on your WooCommerce site and have followed the standard procedure, but you're unable to see all 400 reviews, and old deleted reviews are still visible. Solution: First, ensure you have registered the reviews for translation by following these steps: 1. Navigate to WooCommerce > WooCommerce Multilingual & Multicurrency and select the Status tab. 2. Click the Troubleshooting link at the bottom right corner. 3. In the Troubleshooting tab, check the box next to 'Register product reviews for translation' and click the Start button. 4. Proceed to WPML > String Translation to translate the reviews. If issues persist, our second-tier support can apply a specific SQL query to adjust database tables, which has resolved the issue on a staging site:
ALTER TABLE `rqcv_icl_strings`
CHANGE `language` `language` varchar(7) COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `id`,
CHANGE `context` `context` varchar(160) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `language`,
CHANGE `name` `name` varchar(160) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `context`,
CHANGE `value` `value` longtext COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `name`,
CHANGE `wrap_tag` `wrap_tag` varchar(16) COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `location`,
CHANGE `type` `type` varchar(40) COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT 'LINE' AFTER `wrap_tag`,
CHANGE `title` `title` varchar(160) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `type`,
CHANGE `gettext_context` `gettext_context` text COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `status`,
CHANGE `domain_name_context_md5` `domain_name_context_md5` varchar(32) COLLATE 'utf8mb4_unicode_ci' NULL AFTER `gettext_context`,
CHANGE `translation_priority` `translation_priority` varchar(160) COLLATE 'utf8mb4_unicode_ci' NOT NULL AFTER `word_count`,
COLLATE 'utf8mb4_unicode_ci';
Ensure you have a full backup before applying this solution to your production site.
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 you need further assistance, please open a new support ticket at WPML support forum.
Problema: El cliente está intentando editar atributos de productos en diferentes idiomas, tanto en el idioma principal como en los secundarios, y ha encontrado problemas. A pesar de haber aumentado el límite de memoria a 512MB, sigue enfrentando dificultades. Solución: 1. Verificar si el problema ocurre al editar los atributos en los idiomas secundarios o en el idioma original. Se recomienda seguir los pasos de nuestra guía para crear o traducir atributos en documentación de WPML. 2. Aumentar el límite de memoria de WordPress al mínimo requerido de 128MB, aunque recomendamos 256MB. Agregar el siguiente código en el archivo wp-config.php:
Colocar este código encima de la línea /* That's all, stop editing! Happy blogging. */ Puedes verificar el límite de memoria actual en WPML -> Soporte.
Si esta solución no resuelve el problema o parece no ser relevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: Auf der englischen Version einer WooCommerce-Site fehlt eine Kategorie, obwohl alle Einstellungen wie Permalinks und Tax-Synchronisation überprüft wurden. Lösung: Wir haben festgestellt, dass die fehlende Kategorie 'Lagerprogramm' im Backend unter 'Produkte -> Kategorien' einen Zählwert von '0' aufweist. In den WPML-Einstellungen für den Beitragstyp 'Products' war der Fallback-Modus aktiviert, was bedeutet, dass, wenn keine Produkte übersetzt sind, das Original mit einer übersetzten URL angezeigt wird. Das Problem lag darin, dass es keine übersetzten Produkte gab, weshalb die Hauptkategorie nicht angezeigt wurde. Nachdem ein Produkt übersetzt wurde, erschien die Hauptkategorie. Weitere Informationen und mögliche Lösungsansätze finden Sie unter hier und hier.
Falls diese Lösung nicht relevant ist oder veraltet erscheint, empfehlen wir, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: You are working on a site under development and need to translate estimated shipping days (months) into Latvian using WPML. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Ensure that the strings you want to translate are wrapped in the appropriate gettext functions in your theme or plugin files. For example, use
for WordPress templates. 2. Once the strings are properly wrapped, go to the WPML String Translation page and search for the strings you've added. You should be able to translate them directly there into Latvian. 3. If the strings do not appear in the String Translation list, make sure you have scanned your theme or plugins for strings in WPML. This can be done under WPML > Theme and plugins localization.
If this solution does not apply because it might be outdated or not suitable for 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 you still need help, please open a new support ticket at WPML support forum.
Problem: You are trying to translate estimated shipping days (months) into Latvian on your website, but they are not appearing in Latvian. Solution: We recommend following these steps to locate and translate the strings: 1. Navigate to WPML → String Translation. 2. Enable the option "Look for strings while pages are rendered". 3. Visit the page where the untranslated strings are displayed. 4. Return to WPML → String Translation, disable the option, and check if the string has been registered. 5. Translate the registered string into Latvian. For more detailed instructions, please refer to our documentation on finding strings that don't appear on the String Translation page. Additionally, we have enabled debug information for this support ticket. You can find instructions on how to retrieve this information from your site and provide it to us here: provide debug information for faster support.
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: If you're experiencing discrepancies in stock levels between different language versions of the same product, such as seeing different stock counts in English and Greek for the same item. Solution: First, ensure that you have installed the 'WooCommerce Multilingual & Multi-Currency' addon. You can do this by navigating to Plugins > Add new > Commercial in your WordPress dashboard and installing the addon.
Once the plugin is active, it should automatically synchronize stock and prices across different languages. If the stock levels still do not match, try updating the stock on the original product, as this should correct the stock levels in all languages.
Additionally, check your settings under WPML > Settings > Custom Field Translation to ensure that stock synchronization is configured correctly. Also, visit WooCommerce > WooCommerce Multilingual & Multi-Currency > Support to verify there are no configuration issues.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue where orders created in the admin zone were defaulting to Slovak, despite the admin content being set to English. Additionally, there was a problem with sequential order numbers not being used correctly, with the first number being skipped. Solution: We recommended updating all outdated plugins and the WordPress core. After these updates, we asked the client to verify if the issue was resolved on a Sandbox site. We also ensured that the language information was correctly added to the orders. If you're experiencing this issue, we recommend checking for any outdated plugins or WordPress core updates and ensuring that your WPML and WooCommerce installations are up to date. For further guidance, you can refer to this documentation.
Please note that 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.
Problem: You are trying to translate the Shop Page on your site from Swedish to German using WPML, but the German translation does not save and disappears after reloading the page. Solution: We recommend checking the WooCommerce -> WooCommerce Multilingual & Multicurrency -> Status -> WooCommerce Store Pages section and clicking the button to download the missing German store page. Once downloaded, you can translate the slug of the German shop page in WooCommerce -> WooCommerce Multilingual & Multicurrency -> Store URLs. For detailed guidance, please refer to our documentation on WooCommerce Multilingual & Multicurrency.
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.
