Problem: The client was experiencing an issue where untranslated strings were appearing when filtering for completed translations from English to French on their multilingual website. Solution: We initially attempted to reproduce the issue on a test site but could not replicate the problem, suggesting it might be specific to the client's site setup. We requested access to a staging version of the client's site for a safer and more thorough investigation. Upon further examination, we discovered that the strings were indeed translated, but the display icon was incorrect. To resolve this, we navigated to WPML > Support > Troubleshooting > Cleanup and optimize string table. This action corrected the icon display issue, and the filtering now accurately reflects the translation status.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client wants to delete WPML strings that are not used on the frontend, specifically aiming to remove around 15000 backend strings without affecting frontend translations. Additionally, the client is facing an issue where some strings that appear on the frontend are mistakenly categorized as 'Unknown' in WPML.
Solution: 1. To manage strings that only appear on the frontend, navigate to WPML -> Translation Management -> Strings section. Here, select the option to register only strings that appear in the frontend. 2. To delete unused strings, go to WPML -> String Translations. You can search for strings or filter them by domains, select them, and then delete them using the button at the end of the results table. 3. If you find strings that are on the frontend but categorized incorrectly as 'Unknown', it's important to note that there is no direct option in WPML to re-categorize these strings. These strings might be incorrectly marked due to their creation in the backend.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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.
