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 was experiencing an 'Invalid Post Type' error when trying to translate posts in a custom post type called Reviews. Upon switching the language to English, the error appeared, despite the post type configuration seeming correct. Solution: We resolved the issue by modifying the translation settings for the custom post type. In the WPML -> Settings -> Post Types Translation section, we changed the 'Post Type' (acf-post-type) from Translatable to Not translatable. This adjustment allowed the client to switch and edit a Review post in English without encountering the 'Invalid Post Type' error.
If this solution does not resolve your issue, or if it seems outdated, we recommend 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. Should the problem persist, please open a new support ticket.