Problem: The client's high-traffic corporate website experienced a downtime due to an unexpected traffic spike, with potential issues related to WPML observed in the SQL query logs. It was unclear whether the problem stemmed from WPML or another plugin affecting WPML’s performance. Solution: We recommended increasing the WordPress memory limit to at least 256 MB as WPML requires a minimum of 128 MB. The client was advised to add the following code to the wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
just before the comment:
// That's all, stop editing! Happy blogging.
Additionally, we suggested ensuring all themes, plugins, and WordPress itself are updated to their latest versions to avoid bugs or performance issues. We also recommended checking for any conflicts by switching to a default WordPress theme and deactivating all plugins except WPML and its add-ons and Elementor. If the problem persisted, the client was to activate plugins one by one to identify the problematic plugin. For further details on managing translations and optimizing WPML with caching, we provided links to our documentation:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that their website, which uses the ACF plugin, experiences freezing during the save process when WPML is active. The error message displayed is "Application did not respond in time." This issue does not occur when WPML is deactivated. Solution: We investigated the issue by testing without WPML, ACFML, and with a default theme. The problem persisted, indicating it is not solely related to WPML. We observed that the issue might be related to server resource limitations such as PHP memory limit or server response time. We recommend: 1. Checking the PHP error logs for detailed information on failures. 2. Consulting with hosting support to possibly increase server resources. 3. Considering an update to the PHP version. For issues related to slow performance or increased queries, we suggest consulting this carefully curated list of items. If the problem persists after improving server resources, and you suspect WPML might still be impacting performance, please let us know.
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 issue persists, we encourage you to open a new support ticket at WPML support forum.
Problem: The client reported significant slowdowns on their website when WPML was enabled, despite having a high-performance server setup. The site performed well without WPML and with fewer active plugins, but slowed down considerably when more plugins were activated alongside WPML.
Solution: We conducted a series of tests to isolate the issue, including updating themes, minimal plugin activation, and detailed performance monitoring. It was determined that the performance issue was not caused by WPML itself but by a third-party plugin, specifically 'Ultimate GDPR & CCPA'. This plugin was found to consume a significant amount of runtime due to a function running a regex callback on numerous posts, which severely impacted site performance. We recommended deactivating this plugin or contacting its support for a resolution.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: Вы заметили, что функция WPML_Term_Query_Filter->get_terms() вызывается 80 раз на странице категории WooCommerce, что приводит к 80 SQL-запросам к таблице term_taxonomy и увеличивает время загрузки страницы. Solution: Если вы столкнулись с аналогичной проблемой, мы рекомендуем вам попробовать следующие шаги: 1. Перейдите в WPML → Языки → Make themes work multilingual и временно отключите опцию «Корректировать ID для многоязычного функционала (Adjust IDs for multilingual functionality)». Посмотрите, изменится ли поведение. 2. Перейдите в WPML → Настройки и проверьте, не установлена ли для товаров и категорий товаров опция «Переводимая – использовать перевод, если доступен, или отображать оригинал (Translatable – use translation if available or fallback to default language)». Если установлена, попробуйте изменить её на «Переводимая – отображать только переведённые элементы» и проверьте результат.
Это решение может быть неактуально или не подходить вашему случаю. Мы настоятельно рекомендуем проверить список известных проблем, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохраняется, пожалуйста, откройте новый тикет поддержки.
Problem: Si estás experimentando lentitud en tu sitio web debido a consultas pesadas generadas por WPML, especialmente en las tablas wp_icl_strings y wp_icl_translations, y notas un impacto en el TTFB y el rendimiento general, incluso después de haber desactivado el registro automático de cadenas y limpiado dominios no utilizados. Solution: Te recomendamos crear un sitio staging con una copia de tu sitio en producción para realizar pruebas sin afectar el sitio en vivo. Puedes utilizar el plugin WP Staging, que es gratuito. Una vez establecido el sitio de staging, comparte las credenciales de acceso con nosotros para que podamos revisar e implementar las optimizaciones necesarias. Asegúrate de que la copia del sitio en el staging no incluya imágenes ni archivos extra que aumenten significativamente su peso, limitándolo solo a los archivos esenciales de WordPress, plugins, temas y la base de datos.
Si esta solución resulta irrelevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y verificar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
