Available Solutions

Problem:
The client asked if translating a product using WPML creates two separate products to be operated in the store (one in Polish and one in English), or if there is one product operated in two languages. They noticed that after translating the store, there were separate products for each language, which they had to handle separately.
Solution:
We explained that when a product is translated using WPML, a new product is indeed created and linked to the original one. However, any updates made to the original product, such as price, quantity, stock, and other parameters, are synchronized with the translated product. This means that the client only needs to translate the product text. For more detailed information, we recommended visiting the following links:

• Advanced Information: https://wpml.org/documentation/support/wpml-tables/#language-information-and-translations
• General information about WooCommerce and WPML: https://wpml.org/documentation/related-projects/woocommerce-multilingual/

If the client is referring to specific layout settings being different between languages, these settings are typically controlled by the theme. If the theme uses custom fields to store layout settings for a product, these settings should be set to "Copy" to ensure that the same values are carried over when the product is translated. For further assistance on translating custom fields, we recommended visiting: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/#2-decide-how-to-translate-custom-fields

Please note that the solution provided might be irrelevant due to being 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 for further assistance.

Problem:
You are unable to see untranslated pages in your menu editor or have them considered by the menu sync, even though you have set the post translation setting for pages to be translatable.
Solution:
If you're experiencing this issue, we recommend trying the following steps:
1. Navigate to Appearance->Menus and delete the "translated" menu. This action should allow your menu to display pages in both languages.
2. If the above step does not resolve the issue, consider duplicating the pages temporarily. You can do this through WPML->Translation Management. Select the pages you wish to duplicate and use the batch duplication feature to duplicate them in bulk.

If this solution does not apply to your situation, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if you need further assistance. You can do so at WPML support forum.

Problem:
The client wants a different site logo for each language on their WordPress site using a child theme of Twenty Twenty-One. They have translated the string [theme_mods_acorn]custom_logo with the relevant image ID but are still seeing the same logo across different languages.
Solution:
We recommend using WPML's String Translation to manage different logos for each language. Here are two methods to achieve this:
Method 1:
Navigate to WPML > String Translation. At the bottom of the page, enable the checkbox 'Look for strings while pages are rendered'. Visit the front end of a page displaying the logo, then return to WPML > String Translation and search for the string to see if it appears.
Method 2:
If the string does not appear in WPML > String Translation, it might be categorized as admin text. Follow the guide on finding and translating admin text strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/

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 for further assistance.