Problem: The client logged into their dashboard and received an alert in Italian indicating a problem with some database tables and suggesting contacting WPML support. The symptom described was a 'MySQL server has gone away' error, which was unexpected as no alerts were anticipated. Solution: We recommend the following steps to address the issue: 1. Click the small 'x' icon on the warning message to attempt to remove it. 2. Refresh the dashboard to see if the warning message still appears. If the message disappears, the system is likely functioning correctly. For more detailed information, refer to our documentation: Handling Error Messages About Broken Tables
If this solution does not resolve your issue or seems irrelevant due to being 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You need to remove unused strings from uninstalled plugins that are still present in the WPML string translation. Solution: To delete all the untranslated strings belonging to a particular domain, follow these steps: 1. Navigate to WPML → String Translation. 2. Scroll down to 'Remove strings by domain' and click 'Remove strings'. 3. Select the domains of strings you don’t need anymore and click 'Remove'. This will ensure that the untranslated strings in these domains will no longer appear on the String Translation screen. For more detailed instructions, visit https://wpml.org/documentation/getting-started-guide/string-translation/#how-to-delete-a-string.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to translate ticket descriptions for recurring events using the Events Manager plugin, despite the plugin being marked as compatible with WPML. The issue persisted for years, and previous workarounds suggested by the WPML support team were not effective, especially after plugin updates.
Solution: We have identified a workaround for the issue with translating recurring event tickets in the Events Manager plugin. Our compatibility team has also reached out to the plugin author to discuss integrating this fix permanently. To resolve the issue, please follow the steps provided in the Errata:
We have tested this workaround and confirmed that it allows tickets for recurring events to display correctly in translated versions. If you're experiencing this issue, we recommend you try implementing the workaround provided.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the workaround does not resolve your issue, 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 you still need assistance, please do not hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client encountered a critical error while translating a post using WPML. The error message indicated that the class
WPML_Translation_Jobs_Migration_Repository
was not found in a specific file on their site. Solution: If you're experiencing a similar issue where a class is not found, we recommend checking the file where the class should be located. In this case, the class
. Please download a fresh copy of the WPML plugin and compare the files to ensure they are correct. After verifying the files, reinstall the plugin on your site to see if the issue is resolved. For detailed instructions on how to provide debug information, you can follow our documentation: https://wpml.org/faq/provide-debug-information-faster-support/
