Problema: Si estás experimentando una carga lenta en tus sitios con el plugin WPML, es posible que no sea directamente un problema con WPML, sino con la configuración de tu servidor o con otros plugins. Solución: Te recomendamos seguir estos pasos para identificar y resolver el problema: 1. Incrementa el límite de memoria de WordPress a un mínimo de 512MB. Puedes hacerlo añadiendo el siguiente código en tu archivo wp-config.php, justo encima de la línea /* That's all, stop editing! Happy blogging. */:
2. Verifica el límite de memoria actual en WPML -> Soporte. 3. Si el problema persiste después de aumentar la memoria: - Crea una copia de seguridad del sitio completo - Actualiza cualquier plugin o tema desactualizado - Borra cualquier caché existente - Desactiva todos los plugins, incluyendo los de WPML - Activa un tema por defecto de WordPress, como Twenty Twenty - Reactiva los plugins de WPML - Activa el tema y luego los demás plugins uno por uno, hasta identificar el causante de la lentitud. Si después de seguir estos pasos el problema persiste o si la solución propuesta no es relevante debido a que está desactualizada o no se ajusta a tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos y verifiques que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client is experiencing performance issues due to the 'wpml-scanning-files-hashing' option in the wp_options table being extremely large (over 1MB) and set to autoload, impacting site performance. Solution: This option stores hashes of files related to active themes and plugins to detect changes during the Theme and Plugin Localization scan. It is generally safe to delete or reset this option, and WPML will regenerate it during the next scan under WPML → Theme and Plugin Localization. Disabling autoload for this option by setting autoload='no' should not affect WPML's functionality, although it may revert to autoload after a new scan. If the issue persists or if the size grows significantly again, we recommend opening a new support ticket. For further assistance, 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 this solution does not apply to your case, please open a new support ticket at WPML support forum.
Problem: You are experiencing 504 Gateway Timeouts and significant performance degradation due to increased internal calls to
get_field_groups_by_object_type
after updating WPML and ACF Pro plugins. This issue is linked to how ACFML handles field group translations, especially during REST API requests. Solution: We recommend using the
acfml_should_translate_acf_entity
filter introduced in ACFML version 2.1.4 to selectively disable translation logic during REST API requests. Here is how you can implement it:
It is advisable to add this snippet in a Must-Use plugin for optimal performance. For more details, refer to the official documentation: ACFML filter documentation, and the release notes: ACFML 2.1.4 release.
If this solution does not resolve your issue or seems outdated, 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 for further assistance.
Problem: You are experiencing slow site speed due to over 100 duplicate queries per page when WPML is enabled. Disabling WPML restores normal speed. The issue is traced back to the Bricks theme, particularly its handling of links and calls to
url_to_postid
function. Solution: 1. The issue primarily stems from the Bricks theme, not directly from WPML. The theme generates duplicate queries when checking links for aria attributes, which WPML then filters. 2. Switch to a default theme temporarily to confirm if the issue resolves, indicating the problem is with the Bricks theme. 3. Contact Bricks theme support to report the issue and request a fix. Provide them with details of how the theme's handling of links contributes to the excessive queries. 4. If necessary, Bricks theme developers can collaborate with WPML's developers for guidance on adjusting their code.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML Support Forum.
