Performance

Problem:
The client is experiencing issues with many autoloaded options in the WordPress database related to WPML, as indicated by the WordPress Site Health Status.
Solution:
We recommend checking the "Autoloaded" data from the wp_options table using the following SQL query to identify the size of each autoloaded option (size will be in KB):

SELECT option_id, option_name, sum(char_length(`option_value`))/1024 as size FROM `wp_options` WHERE `autoload` = 'yes' GROUP BY option_id ORDER BY size DESC

After running this query, share the results with us for further analysis. It's important to note that WPML requires its autoloaded data for proper functionality, so we do not recommend disabling autoload for WPML-related options. For other plugins or themes, only consider removing options if they are no longer in use, and always ensure you have a recent backup before making any changes.

If this solution does not apply to your case, or if it seems outdated, please check for 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 issues persist, we highly recommend opening a new support ticket for personalized assistance.

Problème :
Le serveur monte en charge fortement, utilisant intensivement MySQL, ce qui provoque le reboot du service. Les requêtes MySQL sont nombreuses malgré un faible trafic Apache, et cela semble lié à WPML.
Solution :
1. Vérifiez la version de PHP : Assurez-vous que tous les serveurs sont mis à jour vers au moins PHP 7, car la référence à "https://cdn.wpml.org/.fpm/php5.external" suggère qu'un des serveurs utilise encore PHP 5.
2. Examinez le problème avec le plugin GFML : Traitez le problème spécifique lié au plugin GFML en consultant la documentation ici : https://wpml.org/fr/forums/topic/gravity-forms-multilingual-plugin/#post-15898509
3. Envoyez-nous la requête SQL complète qui se produit lorsque le serveur reboot pour une analyse plus approfondie.

Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, 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.

Problem:
The client is experiencing an issue where WPML String Translation is running too many slow queries, as reported by their hosting provider.
Solution:
If you're encountering similar issues, we recommend the following steps:
1. Create a backup of your website, or ideally, test these changes on a staging version to avoid disrupting your live site.
2. Navigate to WordPress Dashboard > WPML > Settings and ensure you select the first option for custom post types, especially for 'products' which currently might be using a less optimal setting.
3. Go to WordPress Dashboard > WPML > Support > Troubleshooting and perform the following actions:
- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Cleanup and optimize string tables
- Click on "Clear invalid strings" to delete unused or invalid strings.

These steps should help reduce the number of slow queries generated by WPML String Translation. If this solution does not apply to your situation, or if it 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 issues persist, please open a new support ticket.

Problem:
The client reported significant slow performance with the WPML plugin activated, particularly when the String Translation plugin is enabled. The issue persisted despite switching themes and disabling third-party plugins. Profiling indicated that the slowdown was related to the ACF Multilingual plugin, specifically with the handling of WYSIWYG fields in custom post types (CPTs).
Solution:
We identified a specific code snippet causing the issue in the ACF Multilingual plugin. We recommended modifying the code in the

ACFML\Field\FrontendHooks::convertTargetLinks

file. The client should locate the line:

if ( $isWysiwygField && is_string( $value ) ) {

and change it to:

if ( $isWysiwygField && is_string( $value ) && strpos($value, 'http') !== false ) {

This change prevents unnecessary processing unless the field contains a link, which should mitigate the performance issue. We are also working on a more permanent solution to be included in future WPML releases.

If this solution does not resolve your issue, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML support forum.