Problem: The client was experiencing issues with their WPML editor where translations were not displaying correctly. They expected to see a column with original language texts and another with translations, but instead, some items showed translations while most displayed the original text. The client had previously set up a staging site and migrated the translation memory, which was treated as a separate entity, causing the main site to lose its translations. Solution: We advised the client that during the staging site setup, they should have selected the option 'I logged in from another domain' to ensure the staging site was connected to the same automatic translation account as the live site. This would have allowed the sites to share the translation memory and avoid re-translating content that was already translated. We provided documentation on how to properly connect websites and share their translation memory: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/. If the client confirms, we can also manually copy the memory back to the live site from our side.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where the Translation Jobs page displayed the error 'Jobs could not be loaded' due to a 'Division by zero' error in the WPML plugin code. This issue occurred after starting a manual translation job, which set the job status to 'in progress' and then closing the tab. Solution: We recommended checking and applying workarounds from similar forum threads:
The client confirmed that updating the status of all jobs from 'in progress' to 'finished' temporarily resolved the issue. We also suggested using a sandbox environment for further testing and to monitor if the issue reoccurs, especially after updates.
If this solution does not resolve your issue or 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.
Problem: You need a simple language switcher with your own styling, but WPML is loading 90 default styles that you have to override. Solution: If you're implementing a custom language switcher and need to prevent WPML's default styles from loading, you can modify the code in your site. Specifically, you can edit the
Add the following code within this method to check if the constant
ICL_DONT_LOAD_LANGUAGE_SELECTOR_CSS
is defined, and if so, return nothing, effectively stopping the CSS from loading:
if (defined('ICL_DONT_LOAD_LANGUAGE_SELECTOR_CSS')) {<br /> return \'\';<br />}
This solution 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
