Problem: The client needs to exclude specific Pages, particularly key landing pages, from automatic translation in WPML while keeping the rest of the site's content automatically translated. These pages require manual SEO translations and custom designs with Elementor, and the client wants to ensure they are not overwritten when the original English content is updated.
Solution: 1. Open the Page you want to exclude (in your default language) in the WordPress dashboard. 2. Change its translation method to use the WPML Editor (Classic or Advanced), then save/update the page. 3. Switch the translation method for the translated version back to the regular WordPress Editor (not the WPML Translation Editor). This action breaks the link with automatic translation for this page. 4. In the translated page’s settings, set the Translation Priority to 'Not needed'. This configuration tells WPML to ignore this translation for future automatic translation or syncs. 5. Edit and save your translated page using Elementor or the standard WordPress editor. Your manual changes will now be preserved, even if you update the original English version later.
To confirm it worked: Make a visible edit to the translated page, save, then update the original English page. Check that your manual translation hasn’t changed. If you see any Elementor warning about edits being lost, you can safely ignore it now—your changes will remain.
Repeat these steps for any other Pages you want to protect. This method keeps your custom translations safe and ensures auto-translate continues to work everywhere else.
If this solution does not apply to your case, 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem:
I am experiencing a significant issue with my website, specifically with the translations of custom post types (CPTs). After running a script for importing external XML records, the post IDs of our CPTs were inadvertently changed. This resulted in all our automatic translations, for which we spent over 140,000 credits, being detached and no longer visible on the site. The titles, slugs, and content of the original posts remain unchanged. I need guidance on how to recover these translations and reattach them to their respective original posts.
Solution:
Utilize WPML troubleshooting functions, such as fixing post type assignment and setting language information, to reconnect the broken links between original posts and their translations. For future translations, you can either assign them manually to a translator or use automatic translations, which will utilize previously translated content from your translation memory, thus avoiding additional charges. Ensure that your script excludes posts created by WPML to prevent accidental deletion of translated posts.
