Performance

Problem:
The client is experiencing a 504 timeout error when updating Formidable Forms on their site. This issue is traced back to the WPML string registration process, specifically the

wpml_register_single_string

function, due to a large number of translation strings (over 90,000) in the WPML database. Each form save processes this entire collection, exceeding the server's PHP execution timeout limits.
Solution:
1. Update the WPML main plugin to version 4.8.5 for performance improvements. Instructions for updating can be found at https://wpml.org/faq/install-wpml/#automated-updates.
2. Increase the PHP memory limit to at least 512M. Add the following code to the "wp-config.php" file:

/** Memory Limit */<br />define('WP_MEMORY_LIMIT', '512M');<br />define('WP_MAX_MEMORY_LIMIT', '512M');

3. Optimize the String Translation table via WPML > Support > Troubleshooting in the WordPress Dashboard.
4. Test the site on a staging version and deactivate all plugins except WPML Multilingual CMS, WPML String Translation, Formidable Forms, and Formidable Forms Multilingual to check if the issue persists.
5. If necessary, consider upgrading to a higher tier of hosting resources.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also 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 https://wpml.org/forums/forum/english-support/.

Problème :
Le client utilise WPML pour traduire des chaînes de caractères sur son site et a cessé d'utiliser WPML pour WooCommerce en raison de problèmes de performances. Le plugin WPML génère un grand nombre de requêtes dans la base de données, ralentissant le site.
Solution :
Nous avons analysé les captures d'écran fournies par le client et confirmé que, bien que WPML augmente le nombre de requêtes SQL, le temps d'exécution ajouté reste minime. Nous avons observé que l'absence de cache d'objets persistant, comme Redis ou Memcached, peut augmenter la charge sur la base de données. Nous recommandons fortement l'activation d'un cache objet Redis pour améliorer les performances. De plus, nous suggérons de réaliser des tests de performance en utilisant des outils comme GTmetrix (https://gtmetrix.com) ou Page Load Time (https://chromewebstore.google.com/detail/page-load-time/fploionmjgeclbkemipmkogoaohcdbig) pour comparer les temps de chargement avec et sans WPML activé. Ces tests aideront à déterminer si WPML est la source principale des ralentissements.

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 confirmer que vous avez installé les dernières versions des thèmes et plugins, et si nécessaire, d'ouvrir un nouveau ticket de support pour une assistance personnalisée.

Problem:
The client reported excessive loading times in the website backend after installing WPML, despite using a default theme.
Solution:
We replicated the client's site in a local environment and found no performance issues with WPML. The problem likely stems from the server environment. Here are the recommended steps:
1. Resolve server errors: Address console errors related to server configuration such as permissions, rewrite rules, and resource limits with your hosting provider.
2. Fix database permissions: Ensure the database user has necessary permissions like CREATE, ALTER, INDEX, and REFERENCES, as indicated by errors in the admin panel.
3. Check plugin file permissions: Confirm that all plugin directories are writable. File permissions should typically be 755 for folders and 644 for files.
4. Increase server resources: Enhance the PHP memory limit, update PHP to a higher stable version, and ensure MySQL/MariaDB versions meet the requirements.
5. Consider alternative hosting: If issues persist, testing the site with different hosting might help, as the local tests showed no issues.

If these steps do not resolve your issue, or if the solution seems outdated, please visit our support forum. We also 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.