Known issue

Problem:
If you're experiencing blank or white pages on product pages using WoodMart custom layouts when WPML is active, and this only occurs with products having many variations (10-15+), while products with fewer variations display correctly, we can help.
Solution:
We recommend updating a specific function in your WPML plugin files. Please locate the file

sitepress-multilingual-cms/addons/wpml-page-builders/classes/Integrations/Elementor/class-wpml-elementor-adjust-global-widget-id.php

and modify the function

duplicate_css_class_with_original_id

around line 132 to the following:

public function duplicate_css_class_with_original_id( $content ) {<br />    $classPrefixes = implode( '|', [ 'elementor-', 'elementor-global-' ] );<br />    $pattern       = '/(class="[^"]*?((?:' . $classPrefixes . ')))(\d+)/';<br />    $result        = preg_replace_callback( $pattern, [ $this, 'convert_id_to_original' ], $content );<br /><br />    if ( null === $result ) {<br />        return $content;<br />    }<br /><br />    return $result;<br />}

After applying this change, please clear any caches on your site to see if the issue resolves. This modification addresses template display failures due to the PHP setting

pcre.backtrack_limit

being exhausted. A permanent fix is anticipated in WPML 4.9.

If this solution does not apply to your case, or if it becomes 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. Should you need further assistance, please open a new support ticket at WPML support forum.

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.