Problem: You are experiencing a Gateway Timeout error when trying to use the Menu Sync feature in WPML. This issue occurs despite the site functioning normally in other aspects, and the PHP timeout is set to 5 minutes, but the gateway timeout happens in 2 minutes and 30 seconds. Solution: We recommend checking with your hosting provider to ensure that the server resources are not being exceeded. Additionally, you can debug performance issues by following the steps outlined in the WPML documentation on how to debug performance problems.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 you still need assistance, please open a new support ticket at WPML support forum.
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.
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.
