Performance

Problem:
The client is experiencing a 504 timeout error when updating Formidable Forms on their site. This issue is traced back to the WPML string registration process, specifically the

wpml_register_single_string

function, due to a large number of translation strings (over 90,000) in the WPML database. Each form save processes this entire collection, exceeding the server's PHP execution timeout limits.
Solution:
1. Update the WPML main plugin to version 4.8.5 for performance improvements. Instructions for updating can be found at https://wpml.org/faq/install-wpml/#automated-updates.
2. Increase the PHP memory limit to at least 512M. Add the following code to the "wp-config.php" file:

/** Memory Limit */<br />define('WP_MEMORY_LIMIT', '512M');<br />define('WP_MAX_MEMORY_LIMIT', '512M');

3. Optimize the String Translation table via WPML > Support > Troubleshooting in the WordPress Dashboard.
4. Test the site on a staging version and deactivate all plugins except WPML Multilingual CMS, WPML String Translation, Formidable Forms, and Formidable Forms Multilingual to check if the issue persists.
5. If necessary, consider upgrading to a higher tier of hosting resources.

If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.

Problem:
El cliente experimenta tiempos de carga extremadamente lentos en el backend, especialmente al guardar cambios en productos y posts. A pesar de desactivar el plugin Nginx Helper y ajustar configuraciones, los tiempos de carga siguen siendo altos cuando WPML está activo. Se observó que el archivo wpml-proxy-interceptor.js podría estar contribuyendo a la lentitud.
Solution:
Después de realizar pruebas desactivando todos los plugins excepto los esenciales y cambiando al tema padre, el rendimiento mejoró, indicando que podría haber un conflicto con algún plugin o el tema hijo. Se recomendó al cliente activar gradualmente los plugins y el tema hijo para identificar el causante de la lentitud. Además, se desactivó el archivo wpml-proxy-interceptor.js mediante el código

define('WPML_DISABLE_PROXY', true);

en el archivo wp-config.php, aunque esto no alteró significativamente los tiempos de carga. Se sugiere seguir esta documentación para más detalles sobre cómo depurar problemas de rendimiento: https://wpml.org/faq/how-to-debug-performance-problems/.

Si la solución proporcionada no resuelve el problema o parece desactualizada, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los 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 intermittent high CPU usage spikes on their VPS hosting a multilingual website using WPML. Despite optimizing the site and deactivating most plugins, the issue persists. The client suspects WPML might be causing these CPU consumption problems.
Solution:
We recommended the following steps to address the high CPU usage potentially caused by WPML:
1. **Increase the WordPress Memory Limit:**
- Access your site files via FTP or your hosting file manager.
- Locate the

wp-config.php

file at the root of your WordPress installation.
- Edit the file and add the following line of code just before the line that says

/* That's all, stop editing! Happy blogging. */

:

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

- Save the changes.
2. **Run WPML's troubleshooting tools:**
- Go to **WPML → Support** in your WordPress dashboard.
- Scroll down to the **Troubleshooting** section.
- Perform the following actions one by one, waiting for each to complete before starting the next:
1. **Clear cache**
2. **Sync post taxonomies**
3. **Remove ghost entries**
4. **Fix element collation**
5. **Fix WPML tables collation**
6. **Set language information**
7. **Fix terms count**
8. **Cleanup and optimize string tables**

After completing these steps, monitor your VPS's CPU usage to see if the spikes persist. If the problem continues, 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 the solution provided here becomes irrelevant or if the issue persists, please open a new support ticket at WPML support forum.