Problem: The client is experiencing an issue where the credit card form on the checkout page does not appear correctly in the default language, although it appears fine in the sublanguage. The client questioned if WPML might be conflicting with any plugins. Solution: We have investigated the issue and determined that it is not related to WPML. It seems to be linked to the server environment or the payment methods used. We recommend the following steps to diagnose the issue further: 1. Temporarily deactivate all WPML plugins. 2. Ensure that your WordPress site language is set to English. 3. Visit the checkout page (/checkout/). 4. Check if the credit card form issue persists. If the form appears correctly with WPML plugins disabled, it should also work correctly once you reactivate WPML.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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, do not hesitate to open a new support ticket for further assistance.
Problem: When adding French and German languages to a store, the product categories of the secondary languages display a 404 error page. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML → Settings → Taxonomies Translation. 2. Ensure that for Product Categories, the slugs are translated in the 'Set different slugs in different languages for Product categories' dropdown. 3. Save those settings. For more details, check the related known issue at WPML Errata.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML 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 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.
