Problem: The client reported multiple issues related to WPML and WooCommerce configurations. These included permalink translations, visibility of Yoast SEO fields, source language settings for the shop page, WooCommerce Upsells display in multiple languages, and missing Quick Pay buttons on the product pages.
Solution: For the missing Quick Pay buttons, we recommended the following steps: 1. Navigate to WooCommerce->Settings->Payments. 2. Ensure the 'PayPal Payment Sections -> Product page' is enabled. 3. Check the 'Country availability' setting at the bottom of the page. If it is set to show only for Switzerland, adjust this setting to ensure visibility in other regions.
For other issues, such as permalink structure and Yoast SEO fields, we confirmed that the settings are correct and no obsolete rules are affecting the functionality. We advised maintaining the current configurations and monitoring the site for any further discrepancies.
If the solution provided here 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 issues persist, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported an issue where custom fields for WooCommerce products were not appearing in the Advanced Translation Editor (ATE), despite being recognized and configured as translatable by WPML. This problem was specific to WooCommerce Products, as custom fields for Categories and Tags were functioning correctly.
Solution: We investigated the issue and found that the problem was related to the configuration and synchronization of the translation settings. After thorough testing and adjustments, we managed to resolve the issue, and the custom fields for WooCommerce products began appearing in the ATE as expected. We also addressed a permalink issue by ensuring that the permalink settings were correctly configured to prevent conflicts and redirect loops.
If this solution does not resolve your issue, or if it seems outdated, we highly 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 the problem persists, please open a new support ticket.
Problem: The client needs to synchronize product attributes across translations after importing them using WP All Import into the default language products. Manually saving each product in the admin triggers the synchronization, but this method is not feasible for bulk updates. Solution: We recommend the following steps to handle this issue: 1. Re-run the same import process. Often, this will correctly synchronize the imported data. 2. Use the legacy version of the WPML All Import addon if it fits your workflow. 3. Manually synchronize the attributes via WPML → Taxonomy Translation, although this may automatically create product variations which might not be desirable. 4. Utilize WP-CLI to update the
post_modified
timestamp of the original products, which triggers the synchronization without altering the product data. If these solutions do not resolve your issue or if they become outdated, please check the related known issues, verify the version of the permanent fix, and ensure you have the latest versions of themes and plugins installed. If necessary, do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client is developing an importer to create multilingual WooCommerce variable products using the WooCommerce REST API along with WPML. They aim to replicate the database structure and behavior of products created manually through WooCommerce + WPML. The main issue is that while the backend shows translated attribute labels correctly, the frontend still displays them in English instead of the respective translations (French or Spanish).
Solution: We identified that the issue was due to the way translations were being handled and displayed. To resolve this, we updated the WPML Import Helper plugin on the sandbox. Changes include: - Added a WooCommerce custom attribute label fallback. - Uses translated product
_product_attributes
as the label source. - Added safe product cache refresh helper. - Updated the attribute import endpoints. - Disabled direct WPML package update endpoint. - Adapted translation connection to rely on WPML hooks. The client should follow specific steps for importing products and linking translations, which involve creating products and variations in the default and translated languages, then linking and rewriting translated product attributes through specific API endpoints. It would be even better using global product attributes if the products are created by WC REST API requests.
If the solution provided here 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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the price displayed in the Slovenian language version of their WooCommerce site shows €11.16 instead of €10.90 when logged in with a Croatian shipping address, despite both language versions having the same product price set. This discrepancy does not occur in the Croatian language version. Solution: 1. Confirm that both the Slovenian and Croatian product translations have identical, WPML-synced regular prices. 2. Check the WooCommerce Product Price widget on the Elementor single-product template, as it might be using a separate calculation or caching path for variable-product price ranges that doesn't match WooCommerce's core tax resolution. 3. If the issue persists, it suggests a potential problem with the display logic in Elementor or XStore, possibly bypassing WooCommerce's tax calculation under certain conditions. In this case, escalate the issue for specialized review. 4. If disabling all plugins and themes, including WPML, results in consistent pricing, the issue likely lies outside of WPML.
This solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 with us for further assistance.
Problem: The client reported that their top-level category page, set as the 'shop page' in WooCommerce product settings, was displaying correctly in English and Spanish, but the French version was empty, showing only the footer. Solution: We unlinked the French page and created a new French translation. This action resolved the issue, which was likely caused by the original French page being edited with a page builder. We recommend the client to verify if everything is now displaying correctly.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: El cliente tiene una tienda en inglés con productos traducidos al español y enfrenta un problema recurrente donde las imágenes se pierden a pesar de haber ejecutado procesos de WPML como borrado de caché y sincronización. Solution: Primero, identificamos que el modo de traducción estaba configurado en manual y no utilizando el editor de traducción de WPML. Luego, desactivamos el plugin Media Translation, ya que este solo es necesario cuando se utilizan imágenes diferentes para cada idioma. Para resolver el problema de las imágenes que se pierden, recomendamos realizar una actualización masiva para que todas las imágenes se copien a las traducciones. Proporcionamos un video tutorial para guiar al cliente en este proceso: https://kommodo.ai/recordings/wwjlcEgJ7S5INPkDHfRZ
Si esta solución no resuelve el problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is experiencing issues with permalinks in WooCommerce + WPML setup, specifically in the Spanish language. While the permalinks work correctly in Portuguese and English, the Spanish product URLs either generate incorrectly or return a 404 error. Despite the slug translations being correctly configured in WPML, and categories functioning normally, accessing a product within a category leads to errors, including ERR_TOO_MANY_REDIRECTS when attempting to fix via rewrite rules. Solution: We recommend checking the WPML → Settings → Post Types Translation to ensure that the slug for the Spanish language is translated correctly. After confirming this, save the settings again. This action might resolve the issue by correctly generating the rewrite rules for the Spanish products. If the problem persists, please provide the URL of a product that is still returning a 404 error along with the steps to reproduce the problem.
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 continues, do not hesitate to open a new support ticket for further assistance at WPML support forum.