Problema: Al intentar activar y configurar WPML en un sitio de prueba, que es una copia del sitio de producción con un gran volumen de publicaciones y adjuntos, se generan consultas SQL intensivas que provocan un uso excesivo de recursos y errores de tiempo de espera (error 524). Solución: Si estás experimentando un consumo excesivo de recursos durante la activación de WPML en entornos con alto contenido, te recomendamos contactar con tu proveedor de hosting para aumentar los recursos del servidor. Además, desactiva todos los plugins y activa un tema por defecto de WordPress durante la instalación para minimizar el consumo de recursos. Si el problema persiste o la solución proporcionada no es relevante porque está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Para asistencia adicional, no dudes en contactar nuestro foro de soporte en WPML support forum.
Problem: If you're experiencing an issue with your database growing too large due to the icl_translate (4.3 GB) and icl_translation_status (3.2 GB) tables, it might be due to how WPML retains data. Solution: We recommend updating to the latest version of WPML where this issue has been addressed. After updating, you can find a new option to clear old translation data under WPML > Support > Troubleshooting. To update WPML, navigate to Plugins > Add new in your WordPress dashboard, click on the "Commercial" tab, and then click "Check for WPML Updates".
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing performance issues on their site's archive pages, particularly with high load times and frequent errors. The WPML_Element_Translation->maybe_populate_cache() function was being called excessively, resulting in around 1,800 SELECT queries per request, significantly affecting site performance. Solution: We identified that the issue was related to the Adjust ID setting in WPML, which was trying to fetch translated IDs for menu items not set in other languages. To resolve this, we recommended the following steps: 1. Disable the Adjust ID option. 2. Navigate to WPML > String translation > Admin Texts Translation. 3. Locate the default language theme option for the main menu at [theme_mods_motors][nav_menu_locations]primary with ID 207. 4. Add this option for translation and assign the translated menu ID for other languages, such as French ID 253. After applying these changes, the site's load time improved significantly, with pages loading in about 2.5 seconds even with cache disabled. For further details on optimizing SQL queries, you can visit https://wpml.org/faq/how-to-optimize-mysql-queries/.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Проблема: 1. Клиент спрашивал, будет ли опция autoload включаться автоматически при запуске массового перевода в WPML. 2. Клиенту нужно было вернуть значение autoload для wp_installer_settings на 'auto', после того как инструменты оптимизации изменили его на 'no'. Решение: 1. По первому вопросу, мы проверили код плагина и подтвердили, что опция autoload не будет включаться автоматически. Это указано в файле
с параметром 'no'. 2. Для второго вопроса, возврат значения autoload на 'auto' можно выполнить двумя способами: - Через PhpMyAdmin: * Откройте PhpMyAdmin. * Перейдите в базу данных вашего сайта. * Найдите опцию wp_installer_settings в таблице wp_options. * Измените параметр autoload на 'auto'. - Через SQL-запрос: * Выполните следующий SQL-запрос:
UPDATE wp_options SET autoload = 'auto' WHERE option_name = 'wp_installer_settings';
* Если используется нестандартный префикс таблиц, замените его на ваш. * Если 'auto' не принимает, установите 'yes'. Перед выполнением запроса обязательно сделайте бэкап базы данных.
Если данное решение не актуально или не подходит под ваш случай, рекомендуем открыть новый тикет поддержки. Также рекомендуем проверить известные проблемы, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
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: Sie versuchen, die Webseite zu optimieren und stellen fest, dass WPML sehr viele Queries (teilweise über 200) pro Seitenload generiert. Solution: Wir empfehlen Ihnen, die Anzahl der Queries zu reduzieren, indem Sie die betroffenen Queries mithilfe des Debug Bar Plugins identifizieren. Bitte folgen Sie diesem Guide: Wie man das Debug Bar Plugin installiert und verwendet.
Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: 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: O cliente está enfrentando lentidão e travamentos no site após iniciar as traduções com o WPML, utilizando os temas THE7 e WPBakery e o plugin WooCommerce. O site apresentou melhora no desempenho após a desativação do WPML. Solution: Após análise, identificamos que a lentidão não está diretamente relacionada ao WPML. Recomendamos: 1. Atualizar o tema THE7 e o plugin WPBakery, além de outros componentes desatualizados. 2. Otimizar imagens e vídeos, reduzindo seus tamanhos. 3. Implementar técnicas de cache e minificação para melhorar o carregamento do site. 4. Instalar o plugin Query Monitor para investigar consultas lentas e identificar outros possíveis gargalos de desempenho.
Se estas soluções não resolverem o problema ou se a situação descrita for diferente, recomendamos abrir um novo ticket de suporte. Também é altamente recomendável verificar problemas conhecidos em https://wpml.org/known-issues/, verificar a versão das correções permanentes e confirmar que você instalou as versões mais recentes de temas e plugins. Para mais assistência, visite nosso fórum de suporte em https://wpml.org/forums/forum/portuguese-support/.
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.
