Problem: The client is concerned about the high percentage of autoload data related to WPML in their database, questioning the necessity of autoloading certain entries like 'otgs-installer-log' and '_wcml_settings', and expressing concerns about the overall impact on website performance. Solution: We explained that the autoload entries are essential for WPML's functionality and should not be disabled. Although we are continuously working on performance improvements, these entries must remain as they are for now. We clarified that the size of these entries, such as 'icl_sitepress_settings', is relatively small (approximately 3.6 KB) and typical for plugins storing extensive settings. We suggested that the client tests their website's performance with and without WPML using tools like Page Load Time to gauge the actual impact. Additionally, we referenced a similar case discussed in our forums which might provide further insights: WPML forum discussion.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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 WPML Support Forum.
Problem: The client is experiencing slow saving times in the WordPress dashboard when editing slugs with Yoast SEO, with saving operations taking up to 4 minutes. Solution: We recommend trying the workaround provided in the WPML errata for backend slowness and duplicated queries. You can find the details here: WPML Backend Slowness Workaround. After applying the workaround, please test the saving speed while other plugins are deactivated to ensure that no other plugins are affecting the performance.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at WPML 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 WPML Support Forum for further assistance.
Problem: Wenn WPML aktiviert ist, verlangsamt sich das Backend erheblich. Der Kunde fragt, ob das Löschen der wp_icl_background_task Tabelle oder Probleme mit dem W3 Total Cache Plugin die Ursache sein könnten. Solution: Wir empfehlen, das W3 Total Cache Plugin zu verwenden, das für die Nutzung mit WPML zertifiziert ist. Stellen Sie sicher, dass es gemäß unserer Dokumentation konfiguriert ist: Optimieren der Leistung einer mehrsprachigen Website mit W3 Total Cache. Falls Probleme weiterhin bestehen, könnten Sie auch andere kompatible Caching Plugins in Betracht ziehen, die wir empfehlen:
Falls diese Lösungen nicht relevant sind, weil sie veraltet sind oder nicht auf Ihr Problem zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme unter https://wpml.org/known-issues/, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The user is seeing an error in the WPML Advanced Translation Editor Logs indicating a change in your site's URL. This error appears because WPML has detected a URL change and needs confirmation whether the site has been moved or copied. Solution: First, ensure you have a full backup of your site. Then, follow these steps: 1) Navigate to WPML>>Settings>>Translation Editor. 2) Select the Advanced Translation Editor (recommended) option. 3) Go to WPML>>Translation Management. 4) Check if the Site Moved wizard is showing. If it is, select the option for Changing to a New Site URL and complete the wizard steps. For more detailed instructions, please refer to the documentation on using the Advanced Translation Editor when you move or use a copy of your site.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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 WPML support forum.
Problem: The client is experiencing slow site performance due to frequent calls to /wp-json/wpml/tm/v1/ate/jobs/retry and /wp-json/wpml/tm/v1/ate/jobs/sync, which trigger multiple admin-ajax.php calls on every admin page load. Solution: We recommend the following steps to improve performance: 1. Check the ATE Error logs by navigating to WPML->Support->ATE Error logs and review the top 5 logs. 2. Deactivate the plugin 'User Import Export for WooCommerce Add-on' when it is not in use. 3. In WPML > Settings, adjust the 'display as translated' settings for post types, taxonomies, and custom fields to 'Translatable only show translated items'. For example: - Pages: Set to 'Translatable only show translated items' - Downloads Products (product): Set to 'Translatable only show translated items' 4. Disable the WPML Media Translation add-on if you are not using a different image per language. 5. Run WPML troubleshooting actions via WPML->Support->Troubleshooting, specifically: - Set language information - Fix Terms Count - Remove Ghost Entries - Cleanup and Optimize string tables
These steps helped reduce the dashboard loading time from 2.04s to 1.63s with WPML activated.
If these steps do not resolve your issue or if the solution seems outdated, 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.
