Problem: The client is experiencing an issue where the Advanced Translation Editor (ATE) does not load in any browser, including Mozilla Firefox and Chrome, on two different sites. Solution: We recommend clearing the cache on both the server and the browser to resolve the issue.
Please note that the solution provided might be outdated or not applicable to your case. If the issue continues, 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, do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client reported that a string at the bottom of BetterDocs pages was not showing the translation, despite the translation being in place and having worked previously.
Solution: We recommended that the client should first update the WPML plugin and add-ons to the latest version to ensure they have all the latest bug fixes and improvements. We provided instructions for updating and emphasized the importance of backing up the database before proceeding.
If the issue persisted after updating, we suggested the following steps: 1. Go to WPML → String Translation. 2. Enable the option "Look for strings while pages are rendered". 3. Navigate to the page where untranslated strings are displayed. 4. Return to WPML → String Translation and check if the string has been registered. 5. If found, translate the string.
We also provided a link to the documentation for finding and translating strings that do not appear on the String Translation page:
