Performance

Problem:
Die Webseite ist im Frontend sehr langsam, und im Fehlerprotokoll wird mehrfach pro Sekunde derselbe Fehler angezeigt: Active record record not found: Couldn't find Translator with [WHERE `translators_websites`.`website_id` = ? AND `translators`.`email` = ?].
Solution:
1. Stellen Sie sicher, dass alle Admin- und Übersetzerprofile in WordPress vollständig sind, einschließlich gültiger E-Mail-Adressen und Namen.
2. Überprüfen Sie die Ladezeiten der Webseite ohne WPML und mit verschiedenen Plugins, um festzustellen, ob WPML tatsächlich die Ursache für die Verlangsamung ist. In diesem speziellen Fall scheint WPML nicht der Hauptgrund für die langsamen Ladezeiten zu sein, da die Webseite auch ohne WPML langsam lädt.
3. Nutzen Sie WP DEBUG, um nach vorhandenen Fehlern zu suchen und melden Sie diese an die entsprechenden Support-Teams.

Falls diese Lösungen veraltet sind oder nicht auf Ihr Problem zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.

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.