Problem: The client is working on a multilingual project using ACF Options Pages and is facing issues with translating them. They want each language version of the ACF Options Pages to behave like regular posts in WPML, with each having its own version and linked as translations of each other without affecting the content of another language when one is saved.
Solution: We explained that ACF Options Pages behave differently with WPML and cannot be edited directly via the WordPress admin editor. The correct process involves: 1. Setting up the options page in ACF. 2. Populating the values via WordPress admin. 3. Translating the page via WPML > Translation Dashboard. For more detailed guidance, we recommend checking the documentation on translating sites built with ACF, specifically for ACF Options Pages at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#acf-options-pages.
If this solution does not resolve your issue or seems outdated, please open a new support ticket. We also 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. For further assistance, you can contact us directly through the WPML support forum.
Problem: You are using WPML with WooCommerce, Elementor, and the XStore theme and want to translate product category names into Arabic while keeping the products only in English. However, when you translate a product category into Arabic, it shows 0 products in the category carousel on the Arabic version of the site. Solution: First, ensure that you have translated all product categories by creating a dummy product, assigning all categories to it, and sending it for translation. For more details, visit https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/.
If this solution does not apply to your case, or if it 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client translated the footer template using Elementor into Italian and Spanish, but the English version continued to display on the multilingual site. Additionally, the flags for language switching were not appearing on the menu. Solution: We identified that the issue was due to the same Elementor template ID being used across all languages, which was stored in the Customizer setting (footer_template). To fix this, we: 1. Went to WPML → String Translation → Admin Texts and searched for the default language Elementor template ID (589), then added this option for translation. 2. Returned to String Translation and set the ID of the translated Elementor template for the secondary language. This adjustment allowed WPML to load the correct footer template for each language. For further guidance on translating theme options, you can visit our documentation here: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-translate-theme-options/
If this solution does not resolve your issue or seems outdated, we 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 at WPML support forum.
