Problem: The client needs to change the original language of products from Dutch to English in bulk on their multilingual website, to facilitate easier addition of Dutch translations later. Solution: We informed the client that there is no bulk method to change the native language of products. Each product must be individually set to English in the 'Language' section of the product settings. Before changing the language, it is necessary to disconnect any existing translations of the product. Additionally, if the client wishes to use automatic translation features, they should temporarily set English as the site's default language, perform the translations, and then switch back to Dutch as the default.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues and ensuring that you have the latest versions of themes and plugins installed. For further assistance, please visit our support forum.
Problem: The client was experiencing issues with sidebar filter translations not appearing on the category page, despite translations being added in the template. Additionally, after translating WooCommerce categories and ACF content, the translated categories in English were missing products present in the original category, displaying 'no product is present for this category' on the frontend. Solution: We reviewed the settings and found that in WPML -> Settings -> Post Types Translation, 'Products (product)' was set to 'Translatable - use translation if available or fallback to default language', and the same setting was applied for 'Product categories (product_cat)'. However, the categories were translated from Arabic to English in WooCommerce -> WooCommerce Multilingual & Multicurrency -> Categories, which caused the filtering issue. To resolve this, we duplicated some products in WPML -> Translation Management, which made the sidebar display the filtering options correctly. We advised the client to duplicate all other products similarly and apply the same changes to other sites. Additionally, we noted that if the product titles and content in Arabic are changed to Arabic in the future, it is crucial to first disconnect the duplicated English products to avoid displaying English products in Arabic.
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: The client is setting up WPML to translate their site's frontend content from Arabic to English but faces issues with missing content in the WPML Translator. Only the Title and SEO Meta are being fetched, and the main body text is absent. Solution: We found that the in-progress translation of the homepage was likely initiated before the Arabic content was fully added, resulting in missing content. We completed this old job, and now all content should be available for translation when translating the homepage from Arabic into English. Regarding the error message in Settings -> Reading, it indicates the need to create translations for the home and blog pages. Completing the homepage translation should resolve this message. If the client does not display a blog page, they can disregard the message about translating the blog page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
