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.
