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:
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/.
Problem: El cliente experimenta tiempos de carga extremadamente lentos en el backend, especialmente al guardar cambios en productos y posts. A pesar de desactivar el plugin Nginx Helper y ajustar configuraciones, los tiempos de carga siguen siendo altos cuando WPML está activo. Se observó que el archivo wpml-proxy-interceptor.js podría estar contribuyendo a la lentitud. Solution: Después de realizar pruebas desactivando todos los plugins excepto los esenciales y cambiando al tema padre, el rendimiento mejoró, indicando que podría haber un conflicto con algún plugin o el tema hijo. Se recomendó al cliente activar gradualmente los plugins y el tema hijo para identificar el causante de la lentitud. Además, se desactivó el archivo wpml-proxy-interceptor.js mediante el código
define('WPML_DISABLE_PROXY', true);
en el archivo wp-config.php, aunque esto no alteró significativamente los tiempos de carga. Se sugiere seguir esta documentación para más detalles sobre cómo depurar problemas de rendimiento: https://wpml.org/faq/how-to-debug-performance-problems/.
Si la solución proporcionada no resuelve el problema o parece desactualizada, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: Die Website hat erhebliche Ladezeitprobleme, verursacht durch das Überschreiten der Memory Limits und viele Datenbankabfragen von WPML. Zusätzlich beeinflussen fehlerhafte Plugin-Konfigurationen und die Verwendung mehrerer Page Builder die Performance negativ. Solution: 1. Es gibt aktuell ein bekanntes Problem, das im Zusammenhang mit
gzuncompress()
auftritt. Siehe hierzu: https://wpml.org/errata/possible-performance-issue-highlighted-by-unexpected-calls-to-gzuncompress/ 2. Deaktivieren Sie das Plugin 'String Locator', da WPML bereits eine ähnliche Funktion bietet. 3. Vermeiden Sie die Verwendung mehrerer Page Builder, da dies die Performance beeinträchtigen kann. 4. Deaktivieren Sie das 'WPML SEO' Add-on, wenn Sie 'SEO Press' verwenden, da es nur mit 'Yoast SEO' oder 'RankMath SEO' kompatibel ist. 5. Überprüfen Sie die Weiterleitungen auf Ihrer Website, insbesondere die durch SEOPress PRO verursachten, und entfernen Sie veraltete oder unnötige Weiterleitungen.
Wenn diese Lösungen Ihr Problem nicht beheben oder die Informationen veraltet erscheinen, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: https://wpml.org/de/forums/forum/deutsch-support/
Problem: The client was experiencing slow loading times and issues while editing posts on their WordPress site using WPML. Solution: We recommend deactivating the 'Adjust IDs for multilingual functionality' option located in WPML -> Languages -> Make themes work multilingual. This change was tested on a staging site and resulted in significantly improved loading times and no issues when saving changes, even with multiple plugins active. Before trying this, ensure you have a recent backup of your site to prevent any data loss.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket for personalized assistance. Visit our support forum for further help.
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 is experiencing intermittent high CPU usage spikes on their VPS hosting a multilingual website using WPML. Despite optimizing the site and deactivating most plugins, the issue persists. The client suspects WPML might be causing these CPU consumption problems. Solution: We recommended the following steps to address the high CPU usage potentially caused by WPML: 1. **Increase the WordPress Memory Limit:** - Access your site files via FTP or your hosting file manager. - Locate the
wp-config.php
file at the root of your WordPress installation. - Edit the file and add the following line of code just before the line that says
/* That's all, stop editing! Happy blogging. */
:
define('WP_MEMORY_LIMIT', '256M');
- Save the changes. 2. **Run WPML's troubleshooting tools:** - Go to **WPML → Support** in your WordPress dashboard. - Scroll down to the **Troubleshooting** section. - Perform the following actions one by one, waiting for each to complete before starting the next: 1. **Clear cache** 2. **Sync post taxonomies** 3. **Remove ghost entries** 4. **Fix element collation** 5. **Fix WPML tables collation** 6. **Set language information** 7. **Fix terms count** 8. **Cleanup and optimize string tables**
After completing these steps, monitor your VPS's CPU usage to see if the spikes persist. If the problem continues, 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 solution provided here becomes irrelevant or if the issue persists, please open a new support ticket at WPML support forum.
