Versions 4.13 through 4.15 focus on giving you more control over retranslation and fixing edge cases that could cause translations to get stuck.
Retranslate Only What You Need
Let’s say you updated a product description, changed your AI instructions, or switched from OpenAI to Gemini and want to see how it translates differently. Previously, force retranslation wasn’t possible — if you wanted a fresh translation, there was no easy way to do it.
Now you can pick exactly which fields to retranslate. Changed just the SEO description? Retranslate only that field. Updated a product title? Force a fresh translation for that specific field — without touching the rest.
This works both on individual posts and in bulk. Select multiple posts, pages, or products and force retranslate them all at once. The activity log tracks every retranslation so you can see exactly what changed.
Better Handling of HTML in Custom Fields
Some custom fields (like ACF WYSIWYG fields or certain meta fields) contain HTML markup. Previously, the AI could sometimes break this markup during translation — turning formatted content into a mess.
The plugin now automatically detects when a field contains HTML and handles it correctly, keeping your formatting intact after translation.
Bug Fixes
- Fixed an issue where translation jobs could get stuck indefinitely if no translatable content was found — they now complete cleanly instead of hanging
- Fixed unwanted translation tags appearing in AI output
- Improved WooCommerce product variation sync
Update Now
This update is available now for all customers. Go to Plugins → Updates in your WordPress admin, or download the latest version from your customer dashboard.
If you’re not using Polylang AI Translation yet, check it out here.