The client is developing a site and needs translations only on the frontend. They are looking to improve site speed by deleting unnecessary backend translation strings in WPML.
Solution:
If you're experiencing similar issues, we recommend following these steps to delete unnecessary strings to potentially improve your site's speed:
1. Ensure you have a full site backup before making changes. 2. Navigate to WPML → String Translation. 3. Scroll down to the 'Remove strings by domain' section. 4. Click 'Remove strings'. 5. Select the domains you want to delete and click 'Remove'.
This process will remove all untranslated strings in the selected domains, and they will no longer appear on the String Translation screen.
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 issue persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problema: El cliente está intentando optimizar la base de datos debido a su elevado tamaño, originado de una instalación anterior. Se observa un tamaño considerable en varias tablas de WPML como wp_icl_strings (19,6MB), wp_icl_string_translations (11,5MB), y wp_icl_translation_status (3,6MB). El cliente desea saber si es posible optimizar estas tablas y por qué las opciones de optimización en 'Soporte-> Solucionador de problemas' no han tenido impacto. Solución: Las tablas mencionadas almacenan información de cadenas traducidas y generalmente no deberían afectar el rendimiento del sitio. Para optimizar estas tablas, recomendamos utilizar la opción de troubleshooting disponible en WPML -> Soporte -> Enlace 'solución de problemas' -> Botón 'Cleanup and optimize string tables': https://wpml.org/documentation/support/wpml-troubleshooting-options/ Es crucial realizar una copia de seguridad de la base de datos antes de ejecutar esta o cualquier otra opción de troubleshooting. Además, sugerimos contactar a los proveedores de hosting para que incrementen la versión de PHP a la v8.0 o v8.1, que son más rápidas.
Si esta solución no es relevante debido a que podría estar desactualizada o no aplicar en su caso, le 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 tiene instaladas las últimas versiones de temas y plugins.
Problem: The client is trying to optimize their website's performance after installing the AAA Option Optimizer plugin. They noticed several items in the autoload option table generated by WPML plugins that are unused but increasing the autoload size. The client is concerned about the impact of WPML plugins on website performance.
Solution: We recommend that disabling autoload for the items listed, which appear to be unused based on the tool's report, should be safe. Although these options are not large and might not significantly impact performance, disabling them could help if they are indeed unnecessary. Any needed options will be loaded on demand via the
get_option
function and cached for the duration of the request. For further performance improvements, we suggest reviewing additional tips on optimizing site performance here.
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 issue persists, please open a new support ticket.
Problem: The client is experiencing slow performance in the backend of their webshop, particularly after installing WPML Multilingual CMS. They also face occasional 503 errors when updating plugins, including WPML. Solution: If you're experiencing similar issues, we recommend following these steps: 1. Increase the PHP memory limit to match the WP memory limit, as discrepancies can cause performance issues. For example, if your PHP memory limit is 256M, ensure your WP memory limit is also set to 256M. 2. Use a code profiler to identify if WPML or any other processes are resource-intensive. 3. Debug the performance issues using the guide provided by WPML here: https://wpml.org/faq/how-to-debug-performance-problems/ 4. If necessary, clone the site to a staging environment to perform further debugging without affecting the live site. Instructions on how to provide a copy of the site can be found here: https://wpml.org/faq/provide-supporters-copy-site/
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 these steps do not resolve your issue, please open a new support ticket with us for further assistance.
Problem: If you're experiencing significantly increased page loading times when the WooCommerce Multilingual & Multicurrency plugin is activated, it might be due to outdated versions of WPML and other plugins. Solution: We recommend updating WPML to version 4.6.15 and Strings Translation to 3.2.17 as described here: WPML Errata. Ensure all other themes and third-party plugins are also updated to their latest versions. If you use Elementor, update WPML before updating Elementor to version 3.26, as detailed here: WPML Changelog. If problems persist, try testing in a minimal environment: deactivate all plugins except for WPML and its add-ons, WooCommerce, and Elementor + Pro. Reactivate plugins one by one to identify the problematic plugin. Ensure to back up your site before making these changes.
If this solution does not resolve your issue or seems outdated, please check for related known issues at WPML Known Issues and confirm you have the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket at WPML Support Forum for further assistance.
Problem: The client is experiencing performance issues with WPML plugins on their website after migrating to a new server. The site operates faster without WPML plugins, which are essential for their business. The client is using an outdated version of WPML (v4.6.3) with WordPress 6.7 and PHP 7.4. Solution: We recommended the client to update their WPML plugins to the latest version available. This can be done by creating a full backup of the site, navigating to Plugins -> Add new -> Commercial tab, and clicking on the button to look for updates. Additionally, upgrading the PHP version to v8 or v8.1 might help improve performance. After making these changes, it is crucial to double-check if the issue has been resolved. Furthermore, we suggested re-saving the permalinks and flushing the cache memory as additional troubleshooting steps. Detailed steps for troubleshooting WPML can be found here: WPML Troubleshooting Options.
If these solutions do not resolve the issue or if they seem outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
