PHP - WPML

Ce sujet est résolu. Voici une description du problème et de la solution.

Problem:
You are experiencing PHP fatal errors related to memory exhaustion on your website after upgrading to WPML. The errors occur inconsistently across different pages but only in the original language. Despite increasing the memory limit, the issue persists, suggesting a potential loop causing the memory exhaustion.
Solution:
First, try the following steps:
1. Navigate to WPML → Languages.
2. Locate the option **"Adjust IDs for multilingual functionality"** and disable it.
3. Save the changes to apply them.
If the problem continues, implement this code snippet to modify the behavior of the Hummingbird plugin's persistent cache:

add_filter( 'wphb_persistent_cache_groups', function( $persistent_groups ) {<br />    if ( false !== ( $key = array_search( 'terms', $persistent_groups ) ) ) {<br />        unset( $persistent_groups[ $key ] );<br />    }<br />    return $persistent_groups;<br />} );

This code removes the 'terms' group from the cache, which might be contributing to the memory exhaustion.

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

Il s'agit du forum d'assistance technique de WPML, le plug-in multilingue pour WordPress.

Il est accessible à tous, toutefois seuls les clients de WPML peuvent y publier leurs messages. L'équipe du WPML répond sur le forum 6 jours par semaine, 22 heures par jour.

Marqué : Exception

Ce sujet contient 0 réponse, a 0 voix.

Dernière mise à jour par Bruno Kos Il y a 1 mois et 2 semaines.

Assisté par: Bruno Kos.

Auteur	Articles
janvier 13, 2025 à 12:08 pm #16588178
juliaZ-6	Contexte de la question: I am trying to upgrade our website lien caché with WPML instead of Weglot. We prepared this long in advance, with a staging server, and went live on Thursday, January 10th. We are hosted at WPMU. Link to a page where the issue can be seen: lien caché Symptômes: Since the upgrade, we are getting PHP fatal errors of exhausted memory, not consistently nor on the same webpages, but always on the original language, never on translated ones. The errors include: 'PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /var/web/site/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/class-debug-backtrace.php on line 133' and 'PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 262144 bytes) in /var/web/site/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/functions.php on line 139'. After upgrading to a plan allowing 2048 MB, we still get the error: 'PHP Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 20480 bytes) in /var/web/site/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/class-debug-backtrace.php on line 133'. Questions: Is there a sYou will notice that the memory allocation try is the same : 20480 bytes. In the first case we had 512 MB memory limit, now 2048MB. It looks like there is a sort of loop somewhere?ort of loop causing the memory exhaustion?
janvier 13, 2025 à 12:55 pm #16588415
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	Here is the ticket. Please check https://wpml.org/forums/topic/memory-limit-issues-due-to-wpml/page/4/#post-14433023, implement this solution and observe your website in the course of couple of days. Let me know if the issue got resolved or is back again, so we could check. There is something else worth checking: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/#how-can-i-identify-the-plugin-causing-this-and-fix-the-issue After this server error, can you check .htaccess file and compare its contents after you resaved site permalinks?
janvier 13, 2025 à 2:19 pm #16588864
juliaZ-6	Hi Bruno, we have no .htaccess since we are running on WPMUDEV hosting, and they have implemented NGINX on the provided link, we are using hummingBirdPro Cache, were we can exclude pages in caching, not categories see lien caché furthermore there are other "Memory exhausted" issues in the forums: https://wpml.org//?s=exhausted&search=forum https://wpml.org/forums/topic/php-fatal-error-allowed-memory-size-of-5368709120-bytes-exhausted/ https://wpml.org/forums/topic/memory-limit-issues-due-to-wpml/ https://wpml.org/forums/topic/compatibility-between-wpml-and-object-cache-pro/
janvier 14, 2025 à 6:45 am #16591253
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	I see. I am checking this with our 2nd tier to gather some ideas based on your setup, I will update here.
janvier 14, 2025 à 9:57 am #16592140
juliaZ-6	Dear Bruno, Yesterday night, upon discussion with WPMUDEV support we have deactivated object caching as referring to lien caché and https://wpml.org/forums/topic/memory-limit-issues-due-to-wpml/page/3/#post-14433023 by adding in the wp-config.php define( 'WPMUDEV_HOSTING_OBJECT_CACHE_ENABLED', false ); Since then no more issue with memory overflow. That confirms WPML has an issue with object caching feature on servers, in the source language and when it’s configured without directory. Of course the issue seems solved by disabling the object cache, but that is not really cool. It seems WPML supports object caching since version 3.1.9 (2015). Since then some improvements and bug fixes have been regularly pushed in regards to object caching : https://wpml.org/fr//?s=object+cache Is our issue is something you wish to escalate ? that would be greatly appreciated. Many thanks
janvier 14, 2025 à 2:19 pm #16593388
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	What if you enable caching again, disable the "Adjust IDs for multilingual functionality" option under WPML -> Languages, and observe the site for a few days? In the meantime, we are trying to set up a WPMUDEV environment with the possibility of installing WPML and activating Object Cache Pro, so we can investigate this more thoroughly.
janvier 20, 2025 à 2:39 pm #16613999
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	Can you provide us with https://wordpress.org/plugins/all-in-one-wp-migration/ package of your site so we could test this in our testing WPMUDEV environment?
janvier 22, 2025 à 5:55 pm #16624644
juliaZ-6	Dear Bruno, Thank you for you feedback. I activated the plugin, export in currently in progress. How/where can I send it to you in a secure way?
janvier 23, 2025 à 7:44 am #16625837
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	I marked your next reply as private, you can upload it to a service such as Google Drive or Dropbox. But I can also downloaded directly from your site if that is simpler for you.
janvier 23, 2025 à 6:06 pm #16629422
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	I downloaded the package and have sent it to our 2nd tier for further investigation.
janvier 27, 2025 à 7:04 am #16635951
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	We’ve successfully deployed the site; however, we’re unable to reproduce the issues mentioned. Since we’ve migrated from localhost, there are currently no images, and the URL and login details are provided in our previous private reply. We would greatly appreciate your assistance in reproducing the issue to ensure nothing has been overlooked.
janvier 27, 2025 à 3:59 pm #16638614
juliaZ-6	Hello Bruno, Indeed you can't reproduce in a staging environment because of the absence of Stagic Server Cache. In order to reproduce, you need to go in the wp-config.php file in production, and locate the following lines : /* trial for memory exhausted issue on WPML lien caché / define( 'WPMUDEV_HOSTING_OBJECT_CACHE_ENABLED', false ); After you need to put the second line into comments : / trial for memory exhausted issue on WPML lien caché / /define( 'WPMUDEV_HOSTING_OBJECT_CACHE_ENABLED', false ); */ Then you will reproduce the issue
janvier 28, 2025 à 7:23 am #16640007
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	Thank you for the info, let me see if we can reproduce the issue using these constants.
janvier 28, 2025 à 12:54 pm #16641764
Bruno Kos Supporter Les langues: Anglais (English ) Allemand (Deutsch ) Français (Français ) Fuseau horaire: Europe/Zagreb (GMT+02:00)	So it should be like this? define( 'WPMUDEV_HOSTING_OBJECT_CACHE_ENABLED', false ); While testing this should not be commented? This disables object caching to troubleshoot the memory issue?
janvier 28, 2025 à 1:24 pm #16641928
juliaZ-6	this line : [define( 'WPMUDEV_HOSTING_OBJECT_CACHE_ENABLED', false )] without PHP comments deactivate the WPMUDEV object cache, thus solves the issue. By commenting this line, the object caching is activated again attached forum discussion with WPMUDEV