Problem: The client is using WPML 4.8 with String Translation on a WordPress Multisite hosted on SiteGround. Several subsites were experiencing 502 errors, large php_errorlog files with repeated entries, and a 'Database is limited' warning. The main multisite database had exceeded 1 GB, causing temporary blocking of INSERT/UPDATE queries. Despite running cleanup and repair tools, the issues persisted. Solution: We recommended following the steps in our optimization guide to address the database issues. The guide includes deleting obsolete strings, optimizing WPML tables, and clearing caches. These steps are detailed in our documentation, which can be accessed here: Optimizing WPML Database Tables. If the problem persists or recurs, we suggested taking a copy of the site and database for further investigation. Additionally, we requested temporary admin and FTP access to perform a more thorough check.
Please note that the solution provided might be outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum.
Problem:
The client is experiencing issues with archive pages loading incorrectly in the Arabic version of their website. Posts initially load to the right and then shift to the left. This behavior does not occur on the English version of the site, and persists even when all plugins except Avada and WPML are disabled. Solution:
We suggested that the problem might be related to the theme's handling of RTL (Right-to-Left) styles rather than an issue with WPML. To test this theory, we recommended deactivating WPML and setting the Arabic language in Settings → General to see if the issue persists. If the problem is confirmed to be theme-related, we advised considering the addition of a loader to the website to ensure pages are fully loaded before being displayed.
Additionally, we asked the client to check the Avada theme settings for the Arabic language to ensure that there are no discrepancies between the settings for the Arabic and English versions. We requested that the client provide detailed feedback or a screencast to pinpoint the exact issue if it continues after checking the settings.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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.
Problem: The client is using the WP Editor to translate posts and pages from English to Arabic and notices that there are 20 pages of queued translations in the WPML Translation tab, despite the fact that these have already been translated. The client is concerned about why these are showing up and if there are any negative impacts or if they can be ignored.
Solution: We explained that the "Translations" section in WPML is designed to give a comprehensive overview of the translation status for all content. It allows users to see which translations need updates, view completed translations, edit translations, and manage translation jobs. We reassured the client that the pages listed in that section do not have any negative impact on the site. However, we advised paying attention to any translations marked as "Needs Update" and to update them as necessary. Other than that, the client can ignore the rest of the list without concern.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If after checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
