Problem: The client was unable to load translation jobs in the WPML translation editor, encountering an error message stating 'jobs could not be loaded' and a critical site error. Despite increasing memory and resynchronizing the site key, the issue persisted, indicated by a DivisionByZeroError in the WPML plugin's REST API. Solution: 1. We advised checking the WPML->Support->ATE error logs for the top three errors to identify potential causes. 2. We recommended increasing the WP_MEMORY_LIMIT to at least 256M, following the guide at https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#how-to-increase-your-sites-memory-limit. 3. We suggested enabling the WordPress debug log to capture any specific errors related to WPML, providing steps to configure WP_DEBUG settings. 4. The issue of the key mismatch was addressed by instructing the client to delete the existing site key, unregister WPML from their site, and register again with a new key. 5. We identified this as a known issue similar to other cases discussed in WPML forums. We recommended trying the workaround suggested in those threads after ensuring a full site backup.
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. Should the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with skipped translations on their website, where URLs, images, and texts revert to the original language instead of staying translated. Additionally, there are problems with forms disappearing after translation. Solution: 1. Ensure consistent use of translation methods across the website. It is important not to mix manual translation methods with the WPML editor on the same page. For manual translation, refer to this documentation. 2. For translating media such as images, use the WPML Media Translation extension as outlined in this guide. 3. Disable object caching while performing translations to prevent issues. 4. If issues with forms persist after deciding on a translation method, consider opening a new support ticket specifically for that issue.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client was unsure whether to use the WPML editor or the manual translation method for a form page and whether it's possible to use different methods for different pages without mixing them on the same page. Solution: We advised the client that they are free to choose the translation method that best suits their needs, whether it's the WPML editor or manual translation. It's important not to mix translation methods on the same page. For the specific issue mentioned, downloading the WPML Media translation extension resolved the problem.
Please note that 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 the issue persists, please open a new support ticket.
