Problem: The client is experiencing a '400 bad request, request header or cookie too large, nginx' error after opening 4-6 pages in the WordPress admin. This issue started after installing WPML and persists until cookies are cleared, but reappears upon further navigation. Solution: We recommend checking if this issue occurs across different browsers such as Chrome, Firefox, and Safari. Although we couldn't find a similar case in our records, we suggest following the steps in these articles to troubleshoot and potentially resolve the issue:
If these steps do not resolve the issue, it might be due to an outdated solution or a different underlying problem. We highly recommend checking 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: Si estás experimentando lentitud en tu sitio web, con tiempos de carga de página de 8 a 11 segundos, y has identificado un gran volumen de peticiones de admin-ajax desde WPML como posible causa. Solution: 1. Realiza una copia de seguridad completa de tu sitio. 2. Actualiza todos los plugins y temas que puedan estar desactualizados. 3. Ve a Plugins -> Añadir nuevo -> Pestaña 'Comercial' -> Actualiza los plugins de WPML. 4. Borra toda la memoria cache. 5. Incrementa el límite de memoria de WordPress a un mínimo de 128Mb. Puedes hacerlo añadiendo el siguiente código en el archivo wp-config.php, justo encima de la línea /* That's all, stop editing! Happy blogging. */:
6. Verifica el límite de memoria de WordPress en WPML -> Soporte.
Si esta solución no resuelve tu problema o si crees que la información puede estar desactualizada, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client reported slow performance on their site when WPML String Translation is enabled. They noticed that the site is faster when WPML core or WPML String Translation is disabled. They also mentioned that disabling WP Rocket and WPML sticky links did not improve performance. Solution: We conducted initial tests and observed a significant increase in the number of queries when WPML String Translation is activated, mainly due to the SupportCandy plugin. This plugin was making excessive database queries due to its handling of custom fields. We recommended disabling the SupportCandy plugin temporarily to see if performance improves. Additionally, we advised the client to contact SupportCandy's support for a more permanent solution, as they might be aware of the issue. We also suggested that the client could try deleting duplicate rows in the
wp_psmsc_custom_fields
table to reduce the load.
If this solution does not resolve the issue or seems irrelevant due to updates or different configurations, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was encountering a fatal error when trying to open the WPML/Languages menu item in their WordPress site. The error message indicated a call to an undefined function 'wpml_tm_load_tp_networking()'. Solution: We recommended the client to manually download and reinstall the 'WPML Multilingual CMS' plugin from the WPML account downloads section. Despite reinstallation and cache clearing, the issue persisted. We then accessed the site with the client's permission to investigate further. After troubleshooting, we added a function to recreate any missing WPML tables in the database, which resolved the issue on the live site. We advised the client to apply the same workaround on the staging site and to deactivate and reactivate all plugins to ensure the cache was flushed.
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.
Problem: The client is experiencing slow site response times of 10-12 seconds when using the WPML and String Translation plugins. The issue persists even after upgrading the server, enabling caching, and creating a staging site. Deactivating the String Translation plugin resolves the issue, indicating it as the source of the slowdown. Solution: We performed several steps to address the issue: 1. Ran the WPML troubleshooting option to "Cleanup and optimize string tables" at WPML > Support > Troubleshooting, and created the necessary custom language MO files at /wp-content/languages/wpml, which improved site performance. 2. Suggested cleaning up the database by following the steps outlined in this documentation. This includes installing a recommended plugin and running the cleanup process multiple times. 3. Provided a SQL query to delete untranslated strings from the WPML String Translation:
DELETE FROM wp_icl_strings WHERE status = 0;
4. Identified that the custom theme significantly increases load times when enabled. Recommended switching to a default theme like Twenty Twenty-Four, which reduced load times to about 2 seconds. 5. Noted an issue in the custom theme's code and provided the correct usage:
If these solutions do not resolve the issue or if they seem 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 the problem persists, please open a new support ticket.
