Problem: The client is experiencing timeouts with Cloudflare when using WPML to synchronize and translate menus due to high resource usage and extensive database queries. This issue is exacerbated by the n+1 query problem with a large number of menu options and languages. Solution: We recommend the following workarounds to address the timeout issue: 1. Manually translate the menu to avoid triggering the resource-intensive synchronization process. 2. Temporarily disable Cloudflare while running the menu synchronization or translation process, which will prevent Cloudflare from stopping the request. 3. Consider upgrading to Cloudflare Pro, which allows for a higher timeout limit (up to 100 seconds), potentially preventing these interruptions.
If these solutions do not resolve your issue or seem 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 at WPML support forum for further assistance.
Problem: The client is not receiving email notifications anymore and needs clarification on the correct media settings in WPML. Solution: For the media settings, we recommend setting Media (attachment) to 'Translatable (only show translated items)'. This setting ensures that WPML does not duplicate the actual image files but may duplicate media metadata (such as title, alt text, captions, and descriptions) for translation, depending on how the media is used. This approach has no significant impact on database size and does not create duplicate files on the server. For more details, please visit WPML Media Translation documentation. If you're still not receiving email notifications, this solution might be 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 for further assistance.
Problem: The client is experiencing a PHP fatal error when updating translations on their WPML-powered site. The error message indicates an issue with an object expected to be a Collection, array, or object. Solution: Navigate to WPML > Translation Management > Jobs, order the jobs by status, and ensure no job is still assigned to a translation of a target language that no longer exists on the website. Cancel any outdated jobs.
If these steps do not resolve the issue or if the errors reoccur, the solution might be 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 problem persists, please open a new support ticket for further assistance.
Problem: The client is experiencing a critical site error due to two different ATEs being created with different strings, causing issues with translation jobs. Additionally, there are problems updating WPML plugins. Solution: We recommend the following steps to resolve the issues: 1. Navigate to WPML > Support > Troubleshooting. 2. Perform the following actions: - Synchronize posts taxonomies by selecting 'Pages'/'Posts' from the dropdown before clicking the button. - Clear the cache in WPML. - Remove ghost entries from the translation tables. - Fix element_type collation. - Fix WPML tables collation. - Synchronize local job ids with ATE jobs. - Synchronize translators and translation managers with ATE. - Assign translation status to duplicated content. - Set language information. - Fix post type assignment for translations. 3. Clear the caches from your site and browser. 4. Cancel the in-progress job by following the instructions outlined here. 5. Open the default page in the WordPress editor, make a small change in the Title, save the changes to trigger a translation update, and then update the translation.
If these steps do not resolve the issue or if you encounter further problems, such as errors in the debug log or issues updating the plugin, we recommend checking your user profile settings or refreshing your WPML license data. If necessary, unregister and re-register WPML on your site.
If the solution provided here does not resolve your issue or seems outdated, 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, do not hesitate to open a new support ticket here.
