Problem: The client is experiencing slow backend performance with WPML due to the absence of caching plugins and a high number of backend POST requests. Solution: 1. We recommend providing WPML support debug information from your site. To do this, log in to your site, navigate to WPML → Support, click on the 'debug information' link at the bottom of the page, copy the entire content of the text box, and paste it into our support forum. More details can be found here: https://wpml.org/faq/provide-debug-information-faster-support/. 2. Install the Query Monitor plugin to help identify the source of the slow performance. Share the results with us under three conditions: using your website as is, with WPML disabled, and with all other plugins disabled except for WPML. Ensure you back up your site or test on a staging site before making these changes. 3. Review our documentation on boosting the performance of your multilingual WordPress site here: https://wpml.org/tutorials/2022/03/boosting-the-performance-of-your-multilingual-wordpress-site/. 4. Consider using caching plugins, as they are crucial for sites with a large number of languages.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that the sentence of a custom field did not translate into secondary languages. Solution: We advised the client to set the custom field to Translate if it belongs to a product. Here are the steps to follow: 1. Set the custom field to Translate. 2. Edit the original product where the custom field belongs. 3. Make a minor change to the product description, such as adding an extra letter, and update the product. 4. Go to the WPML Advanced Translation Editor; the field will appear there. 5. Translate it and complete the translation. Additionally, ensure that the original system values are copied to the translation and not translated as highlighted in the provided screenshot.
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.
Problem: The client is experiencing an issue where the home page of secondary languages (English for United Kingdom and English for Canada) does not sync the design of the default language. Key sections like banners are missing, and the product showcase does not appear as it does in the default language. Solution: 1. Ensure that all Avada slides and sliders are translated into all languages. This includes translating individual slides and sliders that might be missing in the secondary languages. 2. Use the following URLs to access and translate the slides and sliders:
3. Additionally, translate your products to ensure they are visible and correctly displayed on the front end in the secondary languages.
If this solution does not resolve your issue or seems outdated, we recommend opening 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, please visit our support forum at WPML Support Forum.
Problem: The client's website is set up with English as the default language and uses different currencies based on the language settings. Specifically, the Canadian English version of the site was not displaying the header menu structure after synchronization. Solution: We identified that the Canadian English uses the same base language as the default, which typically does not allow for translation. However, it is possible to duplicate the pages to resolve this issue. We managed to display the default menu by removing the translated but empty Canadian menu. For further guidance on how to duplicate and display untranslated content in secondary languages, we recommend visiting Displaying Untranslated Content on Pages in Secondary Languages.
Please note that this solution might be 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 at WPML support forum.
Problem: If you're experiencing issues where the header product menu dropdown style does not sync across different languages like Netherland, France, Romanian compared to the English version, and you're unsure how to delete the Dutch menu which appears by default, here's what you need to know. Solution: We recommend checking your theme settings as some themes, like Avada, allow setting different theme options per language. To address the synchronization issue: 1. Navigate to Appearance > Menus, edit the translated menus, and save them again. This action often resolves the synchronization issues. Regarding the Dutch menu appearing by default, it's likely because the site's original default language was Dutch, and the menu was created in Dutch. After switching the default language to English, the menu settings might have been disrupted. To resolve this: 1. Go to Appearance > Menus and click the translation icon for the Dutch menu to create a proper translation from the English menu. 2. Use the menu selector at the top to select the Dutch menu you wish to delete and use WordPress's options to delete the menu.
Please note that this solution might be 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 at WPML support forum.
Problem: The client reported an issue with duplicated product listings on their WooCommerce site, visible in the product catalog. The products appeared to be duplicates but had different IDs and titles. Solution: We analyzed the situation and determined that the products were not duplicates created by WPML but were original products that had been translated multiple times. Each product had a unique ID and title, and none of the slugs had the '-2' suffix that would indicate a duplicated product. We recommended that the client clean up the backend by removing any unintended duplicates and verify each product's translation links to ensure they correspond correctly to their original versions. If the issue persists or if the solution provided here is outdated or not applicable to your case, 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. Additionally, if further assistance is needed, please open a new support ticket.
Problem: The client's store default language is English with the currency in USD. They want to display different currencies based on the language, specifically GBP for the UK, without duplicating content or losing automatic translation capabilities. Further, they need to translate the footer. Solution: 1. Set posts and pages to "Translatable - fallback to default language if a translation does not exist" under WPML > Settings > Post Type Translation. This allows the UK content to display the original US content without creating translations or duplicates for the UK. Guide 2. For currency settings, navigate to WooCommerce > WooCommerce Multilingual & Multi-Currency, and under the Currency tab, set a default currency for each language. Guide 3. To ensure the footer links retain the correct language parameter, translate the widgets via WPML > String Translation, selecting the text domain "Widgets". Guide
If this solution does not resolve your issue or seems outdated, please check related 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 for further assistance at WPML support forum.
Problem: If you're experiencing issues with your menu section being messy and showing duplicated menus, Solution: we recommend temporarily disabling WPML and then resaving your main menu. This action has resolved similar issues in the past. However, 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 the problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: If your website's default language is English and it's translated into other languages like French, Dutch, and German using WPML, and all translated product pages show a 404 error, this might be due to incorrect product slug translations. Solution: We recommend checking the translation of your product slugs. Ensure that any placeholders used in the translations match those in the original language. If you find discrepancies, correct the translation, remove any incorrect placeholders, and clear your site's cache. This should resolve the 404 error on translated product pages.
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 issues persist, please open a new support ticket at WPML support forum for further assistance.
