Problema: El cliente está experimentando tiempos de carga lentos al acceder a 'Páginas -> Todas las páginas' en el administrador de WordPress. Utilizando el plugin Query Monitor, se identificaron consultas lentas en los idiomas Catalán e Inglés, relacionadas con el componente de WPML, específicamente con las funciones
WPML_Translation_Job_Factory->add_job_elements()
y
WPML_Translation_Job_Factory->retrieve_job_data()
. Solución: Para resolver este problema, recomendamos seguir estos pasos: 1. Borra toda la memoria caché. 2. Desactiva todos los plugins, incluyendo los de WPML. 3. Activa un tema por defecto de WordPress, como Twenty Twenty. 4. Reactiva los plugins de WPML. 5. Si el problema de rendimiento desaparece, reactiva el tema y luego los demás plugins uno por uno hasta identificar el causante del problema.
Si esta solución no resuelve el problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: The client is managing their database and noticed three lines listed as 'Unused': nid_icl_links_post_to_post, nid_icl_links_post_to_term, and nid_icl_translation_downloads. They are unsure if these can be deleted and are also experiencing high load times on their site. Solution: We recommend not deleting or altering any database tables as these might be used by WPML or other plugins in the future. To address the site's performance issues, we installed the Query Monitor plugin to identify slow queries and ran the WPML Troubleshooting options to clean up the database and fix language assignment errors, which reduced the number of queries and slightly improved site speed. We also found that disabling WPML did not change the load time, indicating that WPML is not the cause of the slowdown. We suggest disabling plugins one-by-one to see which one significantly affects load times. Additionally, we noted that the plugin "Checkout Plugins - Stripe for WooCommerce" is causing warnings and that "Advanced Custom Fields Multilingual" is unnecessary unless "Advanced Custom Fields" is in use.
If this solution does not resolve your issue or seems outdated, please check the related known issues and ensure you have the latest versions of themes and plugins installed. If problems persist, we highly recommend opening a new support ticket here.
Problem: The client installed WPML on their website and experienced significant performance issues. The site became slow and unresponsive, and disabling WPML restored normal performance. The issues persisted despite updating plugins and themes, and the WooCommerce Force Default Variant plugin and the theme Savoy were suspected to be contributing to the problem. Solution: We recommended the client to update all outdated functionalities and provided a checklist to enhance site performance, available at https://wpml.org/forums/topic/how-can-i-improve-performance-of-a-slow-site/#post-15350474. We escalated the issue to our 2nd tier support for deeper analysis. It was found that the WooCommerce Force Default Variant plugin and the nm_template_loop_attributes function in the Savoy theme were causing the issues. We advised against using the WooCommerce Force Default Variant plugin and recommended upgrading WPML plugins to the latest version for performance improvements.
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 problems persist, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client reported that WPML was slowing down their WordPress backend. Despite increasing the PHP execution time and WP Memory Limit, and ensuring all WPML plugins were updated, the backend load times remained unchanged. The client observed three API calls loading on every page. Solution: We recommended the following steps: 1. Confirm the WP Memory Limit is set to 256M or higher, as only 128M was being assigned despite having 1GB available. 2. Increase the PHP Time Limit from 30 to 90 seconds. 3. Ensure all WPML plugins and add-ons are updated by navigating to Plugins -> Add new -> Commercial tab -> Check for updates. 4. After updating, compare the loading speeds with WPML enabled and disabled, and identify where the performance issue persists. 5. Check WPML->Support->ATE error logs for any recent errors and share the top five. 6. Perform the following actions in WPML->Support->Troubleshooting: - Clear the cache in WPML - Remove ghost entries from the translation tables - Set language information - Cleanup and optimize string tables 7. Report back with the results for further assistance.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for personalized assistance at WPML support forum.
Problem: You are experiencing a performance issue with WPML where a GET query to check if the REST API is available is causing the Admin Panel to load very slowly. Despite increasing the WP memory limit to 512M, the issue persists.
Solution: First, ensure that your WordPress memory limit meets the minimum requirements by adding the following code to your wp-config.php file:
You can verify the memory limit in WPML -> Support. If the performance issue continues, follow these steps: 1. Create a full site backup or a staging site. 2. Update any outdated plugins and themes. 3. Flush any existing cache. 4. Deactivate all plugins, including WPML ones, and activate a default WordPress theme like Twenty Twenty. 5. Reactivate the WPML plugins. If the issue resolves, reactivate your theme and other plugins one by one to identify the problematic one.
Regarding your specific questions: 1. Temporarily disabling the REST API check using
can cause unintended issues with WPML functionality. 2. The long duration of the GET request is not due to WPML’s external server response time. 3. There is no way to cache or optimize this request within the WPML interface.
If these steps do not resolve your issue or if the solution becomes outdated, we 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 necessary, please open a new support ticket at WPML support forum for further assistance.
