Problem: You are experiencing low site loading speeds due to the wp-wpml_current_language cookie, which is set only after the first response. This issue prevents the cache plugin from caching the first request. Additionally, the use of multi-currency based on IP also hinders caching. Solution: It is normal for WPML with the multi-currency feature to not serve the first visit from cache. WPML needs the initial request to detect the visitor's correct currency using GeoIP or rules. After the currency is set, all subsequent pages can be fully cached. This behavior ensures that clients can switch currencies, as they would otherwise be served the same cached version with the outdated currency settings. For more details on how caching might affect multi-currency settings in WPML, please visit https://wpml.org/errata/caching-plugins-may-cause-issues-with-wcml-multi-currency-settings/.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 https://wpml.org/forums/forum/english-support/.
Problem: You are encountering a database error on your WordPress site using the WPML plugin, specifically a subquery returning more than one row. This error is linked to a specific SQL query involving multiple conditions and joins. Solution: First, ensure you have a backup of your site. Product entry in DB was corrupted. You should fix it by adjusting language informations in the DB.v For example, following SQL command to correct the source language code of mentioned Product ID in your database:
UPDATE wp_icl_translations<br />SET source_language_code = 'en'<br />WHERE trid = 18002<br /> AND language_code <> 'en'<br /> AND source_language_code IS NULL;
This solution might not be relevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was unable to edit a WooCommerce product in the default language (English) because it was mistakenly identified as a translation of another product. This resulted in locked fields and a non-editable status indicated by a lock icon.
Solution: 1. Check Language Assignments - Navigate to WPML → WooCommerce Multilingual or WPML → Translation Management. - Locate the product and review its language assignments to ensure English is set as the default.
2. Find the Original Product - In the product’s edit screen, check the “Language” box. If it shows as a translation, there should be a reference to the original product. Follow that link to access the original.
3. Restore the Default Language Assignment (if needed) - If necessary, disconnect the English version from being a translation and set it as the main product. - In the “Language” section, select “Change Translation Of” or “Make this the original” and save the changes.
4. Edit Product Details - Once the product is recognized as the original, all fields should become editable. Make the desired changes and save.
If these steps do not resolve the issue or the options mentioned are not visible, it might be due to outdated solutions or a different problem. 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 open a new support ticket at WPML support forum for further assistance.
Problem: The client was migrating their website from one server to another and encountered issues where WPML incorrectly detected the site's URL and displayed errors regarding the default language needing to be mapped to a supported language. Solution: 1. Verify the site URL in WPML settings and ensure it matches the current site URL after migration. 2. Check the default language settings in WPML to confirm it is mapped correctly to a supported language. If issues persist, manual intervention might be required to investigate potential configuration or database issues.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Additionally, please check 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. For further assistance, visit our support forum at WPML Support Forum.
Problem: The client was experiencing persistent loading and sporadic 404 errors on translated pages of their website after using WPML. The issues included pages not displaying after translation and random 404 errors when switching languages. Solution: We recommended the following steps to troubleshoot and resolve the issues: 1. Ensure all pages are correctly translated by making a minor edit in the original language, saving it, and then updating the translation. 2. Check and flush cache settings, as stale cache data might lead to pages not loading correctly. 3. Deactivate and reactivate plugins to identify any that might be causing conflicts, particularly focusing on the 'Razorpay for WooCommerce' and 'Categories Images' plugins, which were found to be problematic. 4. Switch the language URL format settings in WPML to see if this affects the 404 errors. 5. Increase the WordPress memory limit to ensure sufficient resources are available for operations. 6. If issues persist, especially with specific plugins like 'WooCommerce PayPal Payments', deactivate them to check if the problem resolves.
If these steps do not resolve the issues, or if the solution seems outdated or not applicable 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. For further assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to translate an Elementor page on your WordPress site using WPML, but after completing the translation, only a small part of the content is translated, and the rest remains in English. Solution: The issue might be due to custom Elementor Widgets in your theme that are not registered for translation. We recommend registering these widgets manually. You can follow the detailed steps provided in our documentation on how to do this: Registering Custom Elementor Widgets for Translation.
If you find these steps challenging or if they do not resolve your issue, please consider 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. If further assistance is needed, you can contact us directly through our support forum.
