🔗 Replace internal links with the new release of Gato AI Translations for Polylang
Gato AI Translations for Polylang just dropped v15.2, packed with powerful new features and improvements.
Replace Internal Links
When translating posts, internal links pointing to the homepage, other posts/pages, tags, categories, media items, and users in the source language can now be automatically replaced with the corresponding URLs in the target language.
Replacing an internal URL in ACF's Link field is also supported 🙏.
Check out guide Replacing internal links for more details.
Partial Translations
You can now perform partial translations of the content:
- Properties (title, slug, and excerpt)
- Content (post content)
- Meta (custom fields)
This presents several benefits.
Replace internal links without re-translating the content
If you've already translated your content, and you'd now like to replace the internal link URLs, you can do so by unchecking the Translate content option:
Replace entity references in meta or blocks without re-translating the content
Same as above, you can replace the entity ID to point to the target language without re-translating the content, such as when editing a Post object field in ACF, or including a new post to the GenerateBlocks Query block.
Re-translate the post title without re-translating the post content
If you update the title of a post, you can avoid re-translating the content and meta, saving time and API costs:
Newly-Supported Gutenberg Blocks
The plugin now supports additional Gutenberg blocks:
ChatGPT 5.1 (Thinking) Model
Added support for the latest ChatGPT 5.1 (Thinking) model. Translate your content using OpenAI's most advanced model yet.
Translate not-yet-fully-migrated content
You can now translate content that has not been fully migrated across Page Builders, such as from Gutenberg to Elementor, or from the Classic Editor to Bricks.
✅ Translate Elementor Posts Not Built with Elementor
If a Custom Post Type is handled by Elementor, but the post itself was not built with Elementor (and has not been migrated yet), you can still translate it.
✅ Translate the post_content field
Before v15.2, the plugin did not translate the post_content field for Elementor/Bricks (as the widgets/elements are stored in meta). Now you can do so.
Better Polylang Pro Integration
The plugin now automatically keeps the same slug for translation entries (for posts and taxonomies) when using the "reuse slugs" feature from Polylang Pro.
(Previously, you had to update the slug manually after translation.)
Better AI Translations
Two key improvements have been made to enhance AI translations quality:
WP-CLI Updates
The WP-CLI commands have been enhanced with new options:
--fail-if-log-notifications
Make the command fail if there are log notifications (eg: if there was a warning or error). Useful for stopping a batch process if any translation failed.
--parts
Specify which parts of the content to translate (title, content, meta).
--tasks
Execute specific tasks, such as translating content without replacing internal links.
Smaller Logs
The plugin now stores smaller logs by default: It avoids printing the queryExecutionResponse entry, so each log entry weighs just a few KBs.
(You can re-enable it in the Settings.)
And more
Version 15.2 includes several other improvements and bug fixes.
See the changelog for the full list of changes.
As always, enjoy! 🙏
