Problem: The client is experiencing slow website and backend speeds, suspecting that WPML and its translated content might be causing conflicts or using excessive processing/data/storage space. Additionally, there is concern about a large error log related to WPML. Solution: We reviewed the wp-config.php file via FTP and confirmed that the debug.log was enabled but did not show any serious issues with WPML. To prevent the file from growing and potentially causing storage problems, we deactivated the debug.log. We also clarified that the link provided by the client (https://revoltbikes.nl/wp-admin/admin.php?page=sitepress-multilingual-cms%2Fmenu%2Fdebug-information.php) is not an error log but a debug information page useful for our support team. After checking the site's frontend and backend, we did not observe any significant performance issues. We recommend the client specify where the performance issue is noticeable and why WPML is suspected to be the cause for further assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was experiencing 404 errors on newly published translated pages and products with incorrect or inconsistent permalinks. Solution: We recommended checking if the permalinks 'slugs' were correctly translated using the String Translation. It was suggested to reset these URLs to their default settings and then properly translate them. Additionally, we advised deactivating all plugins except WPML and switching to a default WordPress theme to identify any conflicts causing the issue. If the problem persisted, the next step was to create a staging site to further diagnose and resolve the issue without affecting the live site. After these steps, if issues with permalinks still occurred, it was necessary to ensure that slugs for different post types and categories were unique to avoid conflicts.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also contact us directly at the WPML support forum.
