Performance

Problem:
The client is experiencing significant slowdowns in the WordPress admin area due to WPML-related queries, particularly around wp_icl_mo_files_domains and wp_options autoload rows like 'wpml_dependencies:needs_validation'. Despite previous cleanup efforts, heavy queries are still repeating on almost every admin page load.
Solution:
1. Clean up unused MO files and domains by navigating to WPML → Theme and plugins localization and performing a scan of the theme and plugins for strings. After scanning, remove unnecessary files.
2. If performance issues persist, create a staging site to safely test changes without affecting the live site. Use the WP Staging plugin or ask the hosting provider for assistance.
3. Update WPML to the latest version via Plugins -> Add new -> Commercial tab and check if the issue persists.
4. Disable all plugins except WPML and switch to a default WordPress theme to isolate the issue. Reactivate plugins and themes one by one to identify any specific conflicts.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If problems continue, we highly recommend opening a new support ticket for further assistance.

Problem:
El cliente enfrenta un error 500 'Internal Server Error' al intentar abrir 'Traducción de cadenas' en WPML, además de picos altos en el uso de recursos de la base de datos y CPU. La tabla 'wp_icl_string_translations' es muy grande, lo que contribuye al problema.
Solution:
1. Realizar un downgrade de PHP a la versión 8.1 o 8.2 y seguir los pasos de troubleshooting de WPML disponibles en esta guía.
2. Crear un sitio staging para realizar pruebas sin afectar el sitio en producción, utilizando el plugin WP Staging.
3. Solicitar al hosting que ajuste los siguientes parámetros en el servidor de base de datos y reinicie MySQL:
- wait_timeout = 300
- max_allowed_packet = 512M
- innodb_log_file_size = 256M
4. Verificar si el problema persiste en el sitio staging y en producción.

Si la solución proporcionada no resuelve el problema o parece irrelevante 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 revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.

Problem:
The client is experiencing a persistent spinning update icon in the WPML admin area, which may indicate a stuck background process during the use of the WPML Media Translation add-on. The process has been running for an extended period without completion, and the client is unable to proceed with content creation or database backup.

Solution:
1. Refresh the browser to see if the spinning icon persists, as sometimes the UI does not update until you reload.
2. Navigate to WPML → Media Translation to check if the media items appear as expected for translation. If the images are listed, the process might have completed.
3. If the spinning icon continues, visit WPML → Support and look for any error messages or warnings in the debug info section.
4. Try clearing your browser cache and logging out/in to WordPress.
5. If the issue remains, deactivate and reactivate the WPML Media Translation add-on to reset the background process.

After following these steps, ensure that the spinning icon disappears and media items are visible under WPML → Media Translation. You should then be able to proceed with content creation and database backup.

If the problem persists, please check for any error messages and contact us for further assistance. We also recommend visiting our known issues page to verify if your issue is already addressed. Ensure you have the latest versions of themes and plugins installed. If needed, open a new support ticket at WPML support forum.

Problem:
After installing WPML to translate their website, the client's site became very slow. The client wants to know why and how to resolve the performance issue.
Solution:
1. Increase the WP Memory Limit to at least 128MB, ideally to 256MB for optimal performance. Open the

wp-config.php

file and add the following line just before the comment that says '// That's all, stop editing! Happy blogging.':

define('WP_MEMORY_LIMIT', '256M');

2. After updating the memory limit, clear any caches (plugin, browser, and server-side if available), then check your site speed again.
3. If the site remains slow, deactivate all plugins except WPML and its add-ons to check for plugin conflicts. Reactivate them one by one to identify any specific plugin causing slowdowns.
4. Enable object caching and configure a caching plugin like W3 Total Cache for improved performance.

If these steps do not resolve the issue or if the solution 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 the problem persists, please open a new support ticket for further assistance.

Problem:
After migrating to a new hosting, a WooCommerce store operating in three languages experienced significant slowdowns when WPML String Translation was enabled. The site's admin pages often timed out, and there were heavy database queries on icl_strings and icl_translations tables. Additionally, the Advanced Translation Editor (ATE) failed to authenticate, showing repeated auth_error logs.

Solution:
To address these issues, we recommend the following steps:
1. In your WordPress dashboard, navigate to WPML → Settings and check the Translation Editor section for any prompts about reconnecting.
2. Disable string tracking and adjust IDs for multilingual functionality.
3. Use WPML's troubleshooting tools to optimize and clean up string tables, clear invalid and unused strings, and remove ghost entries.
4. Consider using caching plugins and database/object caching where possible.
5. If these steps do not resolve the performance issues, we suggest creating a backup and sharing access credentials with our support team for further investigation.

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 problem persists, please open a new support ticket at WPML support forum for further assistance.