Known issue

Problem:
The client reported a critical error on their site, experiencing a PHP 8.3 infinite recursion issue leading to a 503 error. This was traced back to a potential bug in the WPML plugin with the newer WordPress version.
Solution:
1. We asked the client to check if the issue persists after following the steps described on the erratum page for PHP 8.3.x errors, which can be found here: PHP 8.3.x Fatal Error.
2. We requested a detailed description of the issue, including steps to reproduce it and any error messages, to better understand the problem.
3. We asked for access credentials to the site to investigate the configuration and reproduce the issue.
4. We inquired if the client would prefer to continue troubleshooting the issue or remain on the older WordPress version (v6.8.9) that did not exhibit the problem.

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 WPML 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:
Dynamic content in the blog pages is not translating correctly, displaying code instead of normal text. This issue affects the homepage's blog section and extends to blog and archive pages.
Solution:
If you're experiencing issues with dynamic content not translating correctly in Divi 5, which is still in Beta, this is a known issue. We are actively working on enhancing compatibility with Divi 5. A fix is anticipated in the upcoming WPML 4.9 release. We recommend following the updates and details on this issue at Divi 5 Dynamic Content May Lead to Improper Translation and Divi 5 Global Variables Are Not Translatable.

If this solution does not apply to your case, or if it seems outdated, 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 WPML support forum.

Problem:
After the last update, the website became very slow. Disabling the WPML plugins temporarily resolved the issue, but reactivating them triggered an error related to WP Endpoints and database entries.
Solution:
If you're experiencing this issue, it might be due to one of two reasons: either WPML was previously used and reset, or the database prefix changed. We recommend trying the workaround provided in the following errata. Please ensure that WPML is enabled when applying this workaround. If this does not resolve the issue, or if you need assistance with the workaround, do not hesitate to contact us.

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 problem persists, please open a new support ticket at WPML support forum.

Problem:
The client's site does not meet WPML's minimum requirements, WooCommerce Multilingual & Multicurrency is reported as not installed, and sale prices for variable products are not displayed in English.
Solution:
First, we recommend modifying how WPML filters cookies during its REST check. Adjust the method in

WPML\Infrastructure\WordPress\SharedKernel\Server\Application\CheckRestIsEnabled::getCookiesWithoutSessionId

located in

/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Infrastructure/WordPress/SharedKernel/Server/Application/CheckRestIsEnabled.php

. Replace the method with a version that ignores serialized cookies, allowing the check to pass successfully.

Second, add a Custom WAF Rule in Cloudflare to whitelist the endpoint

/wp-json/wpml/v1/rest/status

. Log in to the Cloudflare Dashboard, navigate to Security → WAF → Custom Rules, and create a new custom rule with the expression

(http.request.uri.path contains "/wp-json/wpml/v1/rest/status")

and set the rule’s Action to: Skip → All remaining custom rules. Clear all caches after this adjustment.

If these solutions do not resolve your issue or seem 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 the problem persists, please open a new support ticket at WPML support forum.