Problem: Клиент обеспокоен тем, что WPML занимает большую часть времени при генерации страниц, больше, чем все другие плагины вместе взятые. Особенно много времени занимает файл
. Клиент спрашивает, можно ли отключить дебаг-функции на сайте, который находится в продакшене, и что еще можно сделать для ускорения работы WPML.
Solution: Мы предложили клиенту предоставить доступ к тестовому (staging) сайту, чтобы мы могли воспроизвести и протестировать проблему. Также мы попросили клиента описать точные шаги для воспроизведения проблемы, включая: 1. Место возникновения проблемы (страница/раздел/тип контента); 2. Действия, которые клиент выполняет шаг за шагом; 3. Ожидаемый и фактический результаты; 4. При наличии — скриншоты или скринкаст.
Если данное решение окажется неактуальным или не поможет в вашем случае, рекомендуем открыть новый тикет в службу поддержки. Также настоятельно рекомендуем проверить известные проблемы, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: The client reported performance issues on their site, suspecting a conflict between the Uncode theme and WPML. After testing with a default theme, the site ran faster, indicating a potential issue with the Uncode theme. Solution: We recommended checking the known issue with the Uncode theme, which involves a high number of database requests. The suggested workaround includes modifying the theme's functions.php file by adding the following line:
We also advised making a full site backup before proceeding with any changes. Despite these efforts, the client experienced no improvement, and further investigation suggested that the performance issues might not be directly related to WPML but could be due to other factors, including a recent Uncode update and a WooCommerce issue.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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.
Problem: The client reported extreme performance issues with their WooCommerce site when WPML Multilingual CMS and WPML String Translation were enabled, causing page load times to exceed 2 minutes. The slowdown was suspected to be due to heavy database queries or translation-related overhead.
Solution: We identified that the AJAX request for WooCommerce Fragments (get_refreshed_fragments) was causing longer load times, as every fragment passed through translation filters. A known bug in WCML caused fragments to refresh multiple times unnecessarily. We suggested a workaround to disable cart fragments if an auto-updating mini-cart was not needed, using the following code:
Additionally, we found that the first uncached page load was extremely slow regardless of WPML being active, indicating a potential issue with the caching setup. We implemented the above workaround in the Child Theme, which improved the load time to about 6 seconds with WPML enabled.
We also recommended ensuring that the WPML Multilingual & Multicurrency for WooCommerce addon was enabled and that WPML and its addons were updated.
If you're experiencing similar issues, we recommend trying the provided workaround and checking your caching setup. It's also important to ensure that all WPML components are up to date. If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please visit our support forum at WPML Support Forum and open 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.
Problème : Le site canaropa.com est devenu très lent et parfois inaccessible. Le client a demandé une analyse pour déterminer si les plugins WPML contribuaient à ces problèmes de performance. Solution : Nous avons constaté que la mémoire et le CPU étaient entièrement utilisés, ce qui indique une surcharge des ressources. Plusieurs plugins ont été identifiés comme sources d'erreurs et de requêtes lentes, ce qui contribue à la lenteur du site. Bien que l'augmentation des ressources serveur puisse aider, nous recommandons de réaliser un audit complet du site pour identifier et éliminer les éléments inutiles. Il est également conseillé de vérifier la base de données pour identifier les tables les plus lourdes et évaluer leur taille appropriée. Nous avons temporairement désactivé WPML pour les tests, et il semble que la mémoire soit toujours très utilisée, bien que jamais entièrement. Pour la configuration actuelle du site et son contenu multilingue, 3 Go de RAM devraient suffire, mais le processeur pourrait nécessiter une évaluation plus approfondie.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à ouvrir un nouveau ticket de support. Nous vous recommandons également de consulter les problèmes connus et de vérifier que vous avez installé les dernières versions des thèmes et plugins.
Problem: The client is experiencing issues with excessive scheduled actions in the WooCommerce 'wp_actionscheduler_actions' table when deleting translations of products in English, which were not removed when the original product in Spanish was deleted. This causes the database to exceed the limit of their hosting plan. Solution: We recommended clearing the cache and deactivating non-essential plugins before attempting to delete products to ensure the site has more resources available. Additionally, we suggested increasing the 'max_input_vars' limit from 3000 to 10000 with the hosting provider. For a more controlled environment, we created a staging site and discovered that the issue stems from a missing 'priority' column in the 'wp_actionscheduler_actions' table. The temporary fix involves running the following SQL command:
ALTER TABLE wp_actionscheduler_actions ADD COLUMN `priority` int(20) NOT NULL DEFAULT 10 AFTER `group_id`;
However, this is a temporary solution, and the client should seek a permanent fix from WooCommerce support.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
