Problem: The client reported that the WPML plugin is loading JavaScript and CSS files externally, which they believed to be against WordPress plugin guidelines and raised concerns regarding privacy policy compliance and potential security risks. Solution: We explained that the WordPress Plugin Guidelines cited do not apply to WPML as it is not hosted on the official WordPress.org directory. The external scripts are served from our own domain and are part of WPML's service infrastructure, ensuring they comply with our privacy policy and do not conflict with data protection laws like GDPR. Regarding security, while acknowledging the theoretical risk if our servers were compromised, we maintain that the assets are securely served via HTTPS from our controlled infrastructure, balancing flexibility and security effectively. We decided not to bundle JS/CSS with the plugin at this time.
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 further assistance is needed, please feel free to open a new support ticket at our support forum.
Problem: The client is concerned about the authorization of WPML to resell API access from Google/Deepl/Microsoft for translation services, due to restrictions on API reselling by these providers. Solution: We clarified that when purchasing WPML translation credits, the client is not buying direct API access or credentials to Google Translate, DeepL, or Microsoft Translator. Instead, they are paying for a WPML translation service that uses these APIs internally on our behalf. WPML holds its own commercial agreements and API credentials with these providers, and the system consumes translations via WPML’s licensed integration — not by reselling or redistributing the APIs themselves. This ensures that there is no risk of the credits becoming unusable due to API reselling restrictions, as WPML manages all API access directly within its own system and licensing.
If this solution does not resolve your issue or 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 WPML's string translation feature was causing server overload by repeatedly flushing the WP cache. This resulted in increased hosting costs due to auto-scaling and deteriorated user experience. The client asked if it was possible to limit update runs to only run on cron and requested a fix to minimize the use of
wp_cache_flush()
and instead delete only necessary data. Solution: We identified that the 'wpml' directory was missing from the '/languages/' folder, which is essential for WPML to load translations properly. We asked the client to confirm the presence of this directory and gather information about any recent changes to their theme, plugins, or hosting environment that might have affected this folder. Additionally, we recommended replacing the use of
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 reported that WooCommerce Multilingual automatically adds all reviews, including unapproved ones, to string translation. This results in thousands of strings with the 'wcml-reviews' textdomain due to spam comments. Solution: We acknowledged the issue but explained that currently, there is no option to limit string translations to only approved reviews. We prioritize development based on the demand and impact across our user base. Since this request is unique and not widely demanded, it is unlikely to be prioritized in the near term.
If this solution does not apply to your situation, or if it seems outdated, we recommend checking for 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 our support forum.
instead of string concatenation. Solution: We recommend updating to WooCommerce Multilingual version 5.5.0 or higher, as this update addresses the issue. If the problem persists after updating, or if this solution does not apply to your case, 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.
If you still need assistance, we encourage you to open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where the admin notice contains an invalid URL, this might be due to the lack of URL arguments on certain pages like the dashboard. Solution: We plan to address this in a future release. Meanwhile, you can use the following workaround:
Additionally, this issue was resolved in WooCommerce Multilingual version 5.5.0.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related 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.
Problem: The client reported an issue related to WooCommerce Multilingual. Solution: We resolved this issue in WooCommerce Multilingual version 5.5.0. If you're experiencing this issue, we recommend updating to this version. Please check the known issues page to verify the version of the permanent fix and confirm that you have installed the latest versions of themes and plugins.
If this solution does not apply to your case, or if it seems outdated, please do not hesitate to open a new support ticket. We highly recommend visiting the WPML support forum for further assistance.
Problem: If you're experiencing issues with the 'icl_string_positions' table's 'position_in_page' column storing absolute paths instead of paths relative to ABSPATH, this can lead to problems when migrating to a new server or in a multi-server environment. This is because the ABSPATH might not be identical on all servers, causing unnecessary writes and duplicate data. Solution: We have managed to reproduce this issue by enabling the settings 'Look for strings while pages are rendered' and 'Track where strings appear on the site', followed by migrating the website to a new domain. We have escalated this issue to our second-tier support for further investigation and to our developers for a permanent fix in future versions. Please be aware that resolving this may take some time.
If this 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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
