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.
