Problem:
The client is having difficulty understanding why some parts of their website are not translating, why some translations appear in the backend but not live, and how to manage translations with WPML and String Translation. They are also unsure about the process of transferring credits after moving from a test site to a production site.
Solution:
If you're experiencing issues with translations not appearing or being partially translated, we recommend consistently using the WPML Translation Editor to avoid errors. For Divi-built pages, ensure the String Translation plugin is installed and activated before translating. If you've already translated pages and then installed String Translation, follow these steps:
1. Open the default page in the WordPress Editor.
2. Make a minor change in the Title and save it.
3. In the language meta section, select the WPML Translation Editor, then click on the Update icon and complete the translation update.
For automatic translations, ensure they are published after review if set in WPML settings. For more information on reviewing automatic translations, visit How to Review Automatic Translations.
Increase the WP Memory Limit to at least 256M to improve translation processing time. Instructions can be found here: How to Increase Your Site's Memory Limit.
For translating widgets, refer to the guide: Translating Widgets.
When moving to a production site, select 'YES' to confirm the site is a copy and transfer credits from the original site. For more details, check: Using Advanced Translation Editor when you move or use a copy of your site.
To transfer credits, you can either transfer them from the test site to your WPML account or remove the site key for the test site in your WPML.ORG account to return the credits. For instructions, visit: How to Assign Automatic Translation Credits to Your Sites.
If this solution doesn't look relevant, please open a new support ticket at WPML Support Forum.
