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.
Problem: The client cannot access the invoices section in WPML > Translation Management > Tools > invoices, as the page remains blank. Additionally, there are errors in ATE logs and concerns about loss of previous human translations and server connection issues.
Solution: 1. We suggest following the method explained in an existing ticket to access invoices: https://wpml.org/forums/topic/invoices-overview-empty-javascript-error/#post-14994701. 2. We recommend making a full backup of the website and updating all available plugins. 3. We found 'CURL error 28' errors in the ATE logs, indicating connection issues with our servers. It is necessary to contact hosting/server support to verify if connections are being blocked by a firewall or similar rules. 4. If the customer needs specific invoices, we can send them by email at the customer's request. 5. If clicking 'check now' on the WPML installer support page shows two green checks, then the connection is fine and the issue might have been resolved by the hosting.
It is possible This solution may not be relevant because it is outdated or does not apply to your case. If so, we suggest opening a new support ticket. We also recommend reviewing known issues at https://wpml.org/known-issues/, Check the version of the permanent solution and confirm that you have installed the latest versions of themes and plugins. If you need further assistance, feel free to contact us on the WPML support forum: https:/ /wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client was experiencing an issue where clicking 'invoices' under WPML > Translation Management > Tools > invoices resulted in a blank page.
Solution: We requested temporary access to the client's site to investigate the issue. After reviewing the site, we asked the client to confirm if all three translation engines were showing up correctly in WPML > Settings > Automatic Translation, and also in WPML > Translation Management > Tools > Automatic Translation Engines. For the separate issue of the invoices page being blank, we created a new support ticket to handle it according to our Support Policy, which states that we should address one issue per ticket.
If you're experiencing similar issues, we recommend checking if all translation engines are visible in the specified WPML settings. If you encounter a blank page when accessing the invoices section, please note that this might be a separate issue that requires its own support ticket.
Please be aware that the solution provided might be 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 necessary, do not hesitate to open a new support ticket with us here.
