Problem: The client is trying to translate strings on their website using WPML and prefers the String Translation method because it allows translating more than 100 strings at once. However, they are not getting the option to use this method and are concerned about the time-consuming process of adding 49K+ translations in batches of 100.
Solution: We recommend using the Translation Dashboard in WPML → Translation Management for sending strings for translation. Currently, the limit for string translation is set to 100 strings at a time. Unfortunately, this limit cannot be increased due to potential usability and performance issues. For now, you must send strings in batches of 100 for automatic translation.
If this solution does not apply to your case, 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 at WPML support forum for further assistance.
Problem: Если вы заметили, что плагин WPML замедляет загрузку страниц на вашем сайте, особенно на крупных сайтах, таких как интернет-магазины. Solution: 1. Убедитесь, что вашему сайту хватает ресурсов. Проверьте минимальные требования для WPML на https://wpml.org/home/minimum-requirements/. 2. Используйте стабильные версии PHP 8 для улучшения производительности. 3. Настройте кэширование с помощью плагинов, таких как Super Cache, W3 Total Cache или WP-Rocket, и включите кэширование объектов через Redis с плагином https://wordpress.org/plugins/redis-cache/. 4. Оптимизируйте HTTPS, используя инструменты типа Better Search Replace или WP-CLI для обновления ссылок в базе данных. 5. Используйте плагин Index WP MySQL For Speed для оптимизации индексов базы данных: https://wordpress.org/plugins/index-wp-mysql-for-speed/. 6. Отключите ненужные плагины и модули WPML, которые не используются активно. 7. Минимизируйте размер страниц, оптимизируя файлы JavaScript и CSS, а также сжимая изображения. 8. В настройках WPML отключите режимы, создающие дополнительные запросы к базе данных, и очистите таблицы WPML согласно инструкциям на странице устранения неполадок. Если проблемы с производительностью сохраняются, мы рекомендуем создать новый тикет в службе поддержки. Также рекомендуем проверить известные проблемы, подтвердить версию исправления и убедиться, что у вас установлены последние версии тем и плагинов. Если нужна дополнительная помощь, пожалуйста, обратитесь в нашу службу поддержки: Форум поддержки WPML.
Problem: The client reported that their site was running slow due to WPML database queries, even after installing WP Rocket for performance enhancement. The specific slow query identified was impacting the site's performance by 0.8-3.0 seconds. Solution: We identified that the slow query was related to translation jobs in WPML that needed review but were not appearing as pending in the translation management. Initially, attempts to fix this using WPML Troubleshooting options were unsuccessful. We then executed an SQL query to remove over 100,000 old translation status entries from the database, which appeared to resolve the issue with slow queries. The SQL command used was:
DELETE FROM `wp_icl_translation_status` WHERE `status` = 9
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing slow update speeds on Elementor pages after adding translations with WPML, even after disabling all other plugins except for Elementor, Elementor Pro, and using the Hello theme. The updates were taking about 1.5 minutes, leading to a 524 server error due to timeout. Solution: We identified that both WPBakery Page Builder and Elementor were active on the site, which can lead to conflicts as it's not advisable to have more than one page builder active. We recommended disabling WPBakery Page Builder if the client plans to continue using Elementor. After disabling WPBakery Page Builder and updating the plugins, the issue was resolved, and the page load time improved to between 4-10 seconds.
If this solution does not resolve your issue or seems outdated, we recommend checking for related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: You are experiencing slow site speed due to a high number of database queries from WPML and String Translation, even after disabling all features. Solution: We recommend contacting your hosting provider and asking them to increase the MaxInputVars value from 1000 to 10000. This adjustment might help reduce the number of queries and improve your site speed. If this solution does not resolve the 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 you still need assistance, please open a new support ticket at WPML support forum.
Problema: El cliente reporta que su sitio web consume recursos de manera desmesurada cuando WPML está activo, aumentando la carga del servidor. A pesar de cambiar de servidor y aplicar medidas como un CDN y caché de objetos, el problema persiste. Solución: 1. Solicitamos al cliente que describa paso a paso cómo reproducir el problema de rendimiento en el sitio. 2. Pedimos al cliente que actualice todos los plugins que estén desactualizados siguiendo este enlace: https://admon.sebastiandeveloper.website/wp-admin/update-core.php 3. Realizamos algunos pasos de troubleshooting para limpiar la base de datos, que pueden consultarse aquí: https://wpml.org/documentation/support/wpml-troubleshooting-options/ Recomendamos al cliente verificar si el problema de rendimiento persiste después de actualizar los plugins.
Si la solución propuesta no resuelve el problema o si la información 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 tiene instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visite nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
