filter not working when URLs contain escaped characters encoded in Unicode with more than two triples of characters, such as %AB%CD%EF.
Solution: We realized that the client translated the URLs using the WPML Translation Editor while using the same URL in each language and this typically results in URLs pointing to the same content across different languages. We also added a new link to the client's test page that worked as expected, indicating that the correct implementation of the filter should resolve the issue. Take note that WPML will by default not display internal links on the WPML Translation Editor and it will auto-adjust the internal links once the contents that are being linked to are translated and published.
If you're experiencing a similar issue, we recommend checking that you are using the WPML Translation Editor to translate your URLs. If the problem persists, it might be due to an outdated solution or a different cause. In such cases, 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 you still need assistance, please open a new support ticket with us.
Problem: The client reported an issue where opening a translation in the Advanced Translation Editor (ATE) and then either making edits or simply opening and closing it without changes, resulted in some of the text on the frontend becoming untranslated. This issue occurred despite the translations being displayed as complete in the ATE. The client mentioned that the affected pages were not top-level pages, had escaped URLs, and contained a significant amount of text and translations.
Solution: We recommended updating the WPML Multilingual CMS, String Translation, and Media Translation plugins to their latest versions, as these have been optimized for compatibility with WordPress 6.5. To update the plugins, the client should navigate to the WordPress admin area and press the 'Check for updates' button on the Commercial Plugins page. If the issue persists after updating, we asked the client to provide steps to replicate the problem so we could attempt to reproduce it on a test site.
Please note that this solution might not be relevant if it's outdated or not applicable to your specific case. If you're still experiencing issues, we encourage you to open a new support ticket. We also 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 you need further assistance, please contact us through the WPML support forum.
