Problem: The client installed WPML on their site but selected automatic translation by mistake. After attempting to reinstall by deleting the plugins, deregistering the site, and reinstalling, some pages still displayed automatic translations that couldn't be edited or saved. Solution: We advised the client that content remains saved in the database even after removing WPML. To achieve a clean installation and remove all previous data, we recommended following the steps for a WPML reset as outlined in our documentation: Deleting Languages and Plugin Data by Doing a WPML Reset on Your Site.
If this solution does not apply to your situation, or if it seems outdated, 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 open a new support ticket at WPML support forum.
Problem: The client added text that was not appearing for translation in WPML. Solution: First, we recommend wrapping the string with the gettext function to make it translatable. For example, use the following code:
Next, follow these steps to ensure the string appears in WPML's String Translation: 1. Go to String Translation. 2. Enable the "Auto-register strings" option. 3. Visit the page on the front end where the string is displayed. 4. Disable the "Auto-register strings" option. 5. Search for the string to translate it. For detailed instructions, please visit our guide on finding strings that don't appear on the String Translation page.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket.
