Bug

Problem:
The client was experiencing an issue where their site did not meet WPML's minimum requirements because the WordPress REST API was not responding correctly. This was initially suspected to be due to WPML's requests to the REST API being blocked or not properly authenticated.

Solution:
1. The client was advised to modify the

WordPressRestApiStatus.php

file within the WPML plugin directory to include cookie authentication in addition to the existing basic authentication.
2. After implementing the suggested changes, the issue persisted, leading to further investigation.
3. It was eventually identified as a false positive caused by a minor bug in WPML's code. A workaround was provided by the second-tier support, and a permanent fix is expected in the next WPML version.

If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
The client is experiencing an issue where the Litespeed cache crawler is only caching pages in the main currency (USD) and not in the secondary currency (CAD), despite having set the

wcml_client_currency

cookie to capture both currencies.
Solution:
We recommended the client to temporarily allow all currencies to be accessible from any location to test if the correct cached version is then served. Additionally, we conducted a test using cURL to ensure that the CAD currency pages are being cached when accessed directly with specific cookies set:

curl -X GET "https://kolekin.com/product/48-x-36-floater-frame-walnut-1-5-depth/" \ -H "Cookie: wcml_client_country=CA; wcml_client_currency=CAD; wcml_client_currency_language=en" > output.html

The test confirmed that the page with the CAD currency was correctly received. We have also communicated with LiteSpeed's support to address this known issue and are awaiting their feedback.

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 the problem persists, please do not hesitate to open a new support ticket for further assistance at WPML support forum.

Problem:
After updating WPML CMS to versions 4.8.5 or 4.8.6 on a multisite, links on the homepage that should direct to posts (custom post types for tours) are instead redirecting to images. This issue was identified when the subsite name 'au' conflicted with an image slug also named 'au'.
Solution:
1. Identify and delete the media item with the slug 'au' in your WordPress media library or directly from the database where post_name is 'au'.
2. If deleting the specific media item does not resolve the issue, consider renaming the slug to avoid conflicts.
3. After making these changes, verify if the homepage links are correctly pointing to the intended posts.

Please note that this solution might become outdated or may not apply to your specific case. If the issue persists, we highly 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 necessary, do not hesitate to open a new support ticket for personalized assistance at WPML support forum.

Problem:
The client reported a fatal error related to Elementor's Global Widgets when WPML is active. The error message indicated a problem with calling a function on a null object within the Elementor Pro plugin. This issue was causing the client's website to break on specific pages.
Solution:
We resolved the issue by updating to the latest version of WPML (4.9.0) and the Strings Translation plugin (3.5.0). We advised the client to check for updates at your-domain.com/wp-admin/plugin-install.php?tab=commercial and click the 'Check for updates' button. It is crucial to make a full backup of the site before proceeding with the update.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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, you can also contact us directly at the WPML support forum.

Problème :
Le client ne pouvait pas installer correctement WPML sur son serveur de développement. Après l'installation via OTGS, les composants semblaient installés, mais WPML n'apparaissait pas dans le menu Wordpress ni dans les extensions. Une installation manuelle a été tentée, WPML apparaissait dans le menu, mais la page de configuration était vide.
Solution :
Nous avons installé WPML String Translation pour le client. Il est nécessaire de vérifier la clé d'inscription, car il semble qu'aucune n'ait été attribuée. Voici le message d'erreur rencontré lors de la vérification :

2026/02/05 1:47:04 PM  AMS Server Communication  Api error missing resource: No sitekey found for this website  0  0  {"errorData":{"status":400,"title":"Api error missing resource","detail":"No sitekey found for this website"}}

Nous avons réinitialisé l'inscription du client. Il est recommandé de se rendre sur cette page et de cliquer sur « register » pour finaliser l'inscription.

Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.