Problem: The client reported an issue where deleted glossary terms were still being "cached" and applied in translations, despite being removed from the glossary. Solution: We advised the client to ensure that the content was not coming from a template but directly from the product content itself. After confirming that the section was indeed added via a template, the client was able to edit the relevant file and retranslate the string. This resolved the issue, and the glossary terms were applied correctly after retranslation. If you're experiencing similar issues, we recommend checking if the content is coming from a template and ensuring that all strings are sent for translation through the Translation Dashboard.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported multiple PHP warnings and a WordPress database error related to the WPML String Translation plugin and database operations. Solution: We identified that the issues are associated with a known bug in WPML version 4.9. We recommend reverting to the previous stable versions of WPML and WPML String Translation until the issue is resolved in the upcoming 4.9.1 release. We have implemented this solution on the staging site, and it appears to resolve the errors. Please verify on your end and contact us if the problem persists or if new issues arise.
Please note that this solution might become outdated or may not apply to your specific situation. We highly 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. If the issue persists, please open a new support ticket.
