Problem: The client is experiencing a performance issue on their website, where the database CPU utilization reaches 100% during the creation or updating of posts. They suspect that WPML may be contributing to this issue. Solution: We recommend the following steps to isolate the cause of the high CPU usage: 1. Create a full site backup or set up a staging site using a plugin like WP Staging. 2. Update any outdated plugins or themes. 3. Flush any existing cache memory. 4. Deactivate all plugins, including WPML ones. 5. Activate a default WordPress theme, such as Twenty Twenty. 6. Enable WordPress debug mode by following the guide at https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ 7. Reactivate the WPML plugins. 8. If the issue is resolved, reactivate the theme and other plugins one by one to identify the culprit. 9. Check for any errors related to the performance issue in the debug.log file within the wp-content folder.
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.
Problem: The client is experiencing slow performance and critical errors when editing blog posts in the dashboard editor, with multiple error logs identified by their host coming from WPML. Solution: If you're facing similar issues, we recommend following these steps: 1. Ensure you have a full site backup or create a staging site using a plugin like WP Staging. 2. Update any outdated plugins or themes. 3. Flush any existing cache memory. 4. Deactivate all plugins, including WPML plugins. 5. Activate a default WordPress theme, such as Twenty Twenty. 6. Enable WordPress debug mode by following the guide here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ 7. Reactivate the WPML plugins. 8. If the issue resolves, reactivate your theme and other plugins one by one to identify the source of the problem. 9. Check the debug.log file in the wp-content folder for any errors related to the performance issue.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: The client reported that their CMS was experiencing significant slowdowns, with page load times reaching 10-20 seconds or even timing out. This issue was particularly evident when the WPML plugin was active. The client suspected that WPML's interactions with external servers for license and translation checks might be causing the delays.
Solution: We recommended a systematic approach to identify the root cause of the slowdown: 1. Create a full site backup or set up a staging site using tools like WP Staging. 2. Update all outdated plugins and themes. 3. Clear any existing cache. 4. Deactivate all plugins, including WPML, and switch to a default WordPress theme like Twenty Twenty. 5. Enable WordPress debug mode by following the guide at https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ 6. Reactivate WPML and monitor for any changes in performance. 7. Gradually reactivate other themes and plugins one by one to pinpoint the specific cause of the issue. 8. Check the debug.log file in the wp-content folder for any errors related to performance issues.
If these steps do not resolve the issue or if the solution seems 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. If problems persist, please open a new support ticket.
Problem: You are experiencing slow loading in the WordPress backend, which you believe is related to WPML. You have noticed errors reported by the query monitor, including a function called incorrectly and translation loading triggered too early. You are looking for a way to disable the automatic loading of certain plugins that you don't need translated. Solution: We have escalated the issue related to WooCommerce Multilingual to our second-level support. The specific error, 'Optional parameter $post_translations declared before required parameter $wpdb is implicitly treated as a required parameter' found in the file wp-content/plugins/woocommerce-multilingual/inc/class-wcml-products.php at line 33, will be addressed in the next version of WooCommerce Multilingual.
If this solution becomes irrelevant due to updates or if it does not apply to your case, 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 issues persist, please open a new support ticket at WPML support forum.
Problem: Sie verwenden WPML auf Ihrer Website und haben festgestellt, dass WPML die längste Ausführungszeit von 1,5 Sekunden aufweist, was 7-mal länger ist als das nächstlangsamste Plugin. Sie möchten wissen, warum WPML so lange braucht und was das Plugin auf der Hauptseite macht. Solution: Die lange Ausführungszeit von WPML ist hauptsächlich auf die Überprüfung und Verarbeitung von mehrsprachigen Inhalten zurückzuführen, auch wenn diese nicht direkt sichtbar sind. WPML prüft, ob Inhalte in anderen Sprachen vorhanden sind oder ob Fallbacks erforderlich sind. Dies geschieht durch Abfragen auf Tabellen wie
icl_translations
und Funktionen wie
wpml_object_id()
. Zur Optimierung Ihrer Website-Leistung mit WPML empfehlen wir: 1) Aktivieren Sie Object Caching (z. B. Redis oder Memcached), um wiederholte WPML-Abfragen effizient zu verarbeiten. 2) Testweise die Option „Adjust IDs for multilingual functionality“ deaktivieren, um zusätzliche Last zu reduzieren. Überprüfen Sie jedoch, ob Ihr Theme danach noch korrekt funktioniert. 3) Die Nutzung eines CDN (z. B. Cloudflare oder BunnyCDN) kann helfen, die Auslieferung von statischen Dateien zu beschleunigen und die Serverlast zu reduzieren.
Diese Lösung könnte aufgrund neuerer Updates oder spezifischer Konfigurationen Ihrer Website irrelevant sein. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie unser Support-Forum für weitere Unterstützung.
Problem: El cliente está intentando activar WPML en su sitio web, pero al hacerlo, el sitio consume una cantidad excesiva de recursos del servidor, alcanzando el 100% de uso de CPU y memoria física, lo que provoca fallos en el back end y el front end, y errores de servidor o de conexión con la base de datos. Solution: Para resolver este problema, recomendamos seguir estos pasos: 1. Cree una copia de seguridad del sitio completo. 2. Actualice cualquier plugin o tema que pueda estar desactualizado. 3. Borre cualquier memoria cache que pueda existir. 4. Active el modo de depuración de WordPress siguiendo las instrucciones en https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/. 5. Desactive todos los plugins, incluyendo los de WPML. 6. Active un tema por defecto de WordPress, por ejemplo, Twenty Twenty. 7. Active los plugins de WPML. 8. Si el problema desaparece, comience activando el tema y luego el resto de los plugins, uno por uno, hasta que el problema vuelva a aparecer y pueda identificar al culpable. 9. Compruebe si aparece algún mensaje de error relacionado con el problema en el archivo debug.log que se encuentra en la carpeta wp-content.
Si después de seguir estos pasos el problema persiste, o si la solución propuesta resulta irrelevante debido a que está desactualizada o no se ajusta a su caso, le recomendamos abrir un nuevo ticket de soporte. También sugerimos 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 los temas y plugins. Para más asistencia, visite nuestro foro de soporte en https://wpml.org/es/forums/forum/soporte-en-espanol/.
