Problem: The client needed to know how to set up WooCommerce products for manual translation instead of using WPML's automatic translation. Solution: 1. You need first to switch from the "Translate Everything Automatically" mode to the "Translate What You Choose" mode in WPML settings to allow for manual translations. If automatic translation is still desired for certain content, you can follow the guide at https://wpml.org/documentation/automatic-translation/#translating-individual-pages-posts-and-other-content-automatically. 2. Make sure that the "WooCommerce Multilingual and Multi-Currency" plugin is installed. You can find more information here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/. 3. To manually create a translation for a product: - Navigate to WooCommerce > WooCommerce Multilingual and Multicurrency > Products tab. - Click the + sign to add a French translation.
If the provided solution does not apply or is outdated, or if you encounter further issues, 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 necessary, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where only the English language option is visible on the frontend. The second language does not appear in the dropdown or footer. Additionally, when attempting to access the French version of the site by typing
domain.com/fr
, the default English site loads instead of the French version. Solution: 1. We recommend checking if the content on the page has been translated and ensuring that the translation is published and not in a 'draft' or 'under review' status. 2. If the translation is finished and published, accessing the URL with the language code (e.g.,
domain.com/fr
) should automatically display the translated version of the site in that language. This is the expected behavior, and no special settings are required for it to work. If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
