AutoLingo — Automatic Translation for Polylang & WPML

wp pdat audit — list all source posts with translation status per language
wp pdat audit --format=csv — same output as CSV
wp pdat translate-missing --dry-run — simulate without creating anything
wp pdat translate-missing — translate only missing translations
wp pdat translate-all — translate or update all source posts
wp pdat translate-options — translate ACF Options Page fields
wp pdat audit-acf — list all translatable ACF fields

cp -r autolingo-polylang-translate /var/www/html/wp-content/plugins/
wp plugin activate autolingo-polylang-translate

Changelog

1.4.3

• Fix: with AutoLingo AI, a translated title or alt text could keep the Markdown code fence the AI wrapped it in (« html …« ). The fence is now removed, also from the translations already in the translation memory
• Fix: when a translation fails, the log now gives the real cause (for example the AutoLingo AI characters of the month used up) instead of « DeepL error », whichever provider failed; WP-CLI shows it too

1.4.2

• Fix: with AutoLingo AI, some translated posts lost their block structure (the block markers came back altered from the AI and were not put back). They are now recovered, or the text is translated again piece by piece

1.4.1

• Fix: translating a post or page that links to another post of the site stopped with a fatal error (since 1.4.0), and the translation was not created

1.4.0

• Premium: AutoLingo AI is included: translation with no API key, 1,000,000 characters a month, packs of 10,000,000 characters from the settings. Used automatically when the selected provider has no key, and last when the others run out of quota

1.3.0

• Image alt and title text inside your content (Gutenberg images, HTML) is translated, in the same call as the rest
• Better translations of short texts: the provider is told what it translates (blog post, page, product, category, menu item, image alt text) — DeepL context, OpenAI / DeepSeek instructions

1.2.0

• Microsoft Translator as a fifth provider (free tier: 2,000,000 characters a month)
• Automatic fallback: when the selected provider runs out of quota (DeepL 456, Microsoft free quota, Google daily limit, OpenAI / DeepSeek balance), AutoLingo translates with the next provider that has a key — DeepL, Microsoft, Google, then OpenAI and DeepSeek. Free DeepL, Google and Microsoft accounts add up to about 3,000,000 characters a month. A provider out of quota is skipped for an hour; any other error is still reported. Can be switched off in the settings.
• The settings page shows every API key field while the fallback is on

1.1.30

• Translate category and tag names when no translation exists yet — when a source term has no linked translation on Polylang/WPML, its name (and description) is now genuinely translated via your provider and created as a real linked term, instead of tagging the translated post with the untranslated source term

1.1.29

• Translate image alt text (_wp_attachment_image_alt) — when the media library item itself has a translated counterpart, its alt text is now genuinely translated instead of left in the source language

1.1.28

• Complete the WP.org asset set — plugin icon and banner were never inside the folder the release pipeline actually syncs to SVN, so the listing showed a placeholder icon and no banner on every release; also adds the 2 missing screenshots (settings page, post list)

1.1.27

• Add estimated time and money saved (vs. a translation agency) to the dashboard widget
• Add a real dashboard-widget screenshot to the WP.org listing (screenshot #3) — previously the listing’s 3 screenshot captions had no images behind them because the release pipeline never synced an assets directory to SVN

1.1.26

• Fix « Tested up to » being stuck at 7.0 — WP.org excludes plugins with an outdated value from search results entirely
• Fix plugin name mismatch between readme.txt and the plugin file header
• Add a dismissible admin notice inviting a WP.org review after 20 successful translations

1.1.25

• Add WPML support via adapter pattern — all translation logic now works with Polylang or WPML, whichever is active
• Introduce AutoLingo_Multilingual_Adapter interface and dedicated adapters for Polylang and WPML
• Skip WPML internal post meta (_icl_, _wpml_) during meta copy, alongside existing Polylang exclusions

1.1.24

• Rename plugin to « AutoLingo — Automatic Translation for Polylang » for clarity
• Rewrite readme copy (title, description, FAQ) to target « Polylang automatic translation »
• Split Features into Free / Pro sections — page builders, SEO, ACF and WooCommerce are clearly marked as Pro

1.1.23

• Fix HTML tags (,

1.1.22

• Add [notranslate]…[/notranslate] shortcode: wrap any passage to have it reproduced verbatim in every language — brand names, codes, or quotes are never sent to the translation API

1.1.21

• Reduce synchronous save time: batch title, content and excerpt into a single DeepL API call instead of three sequential requests (3× fewer HTTP round trips per target language)
• Skip API entirely when post content is unchanged since last translation (hash-based detection)
• Add configurable async translation threshold: posts above N characters are translated in the background via WP-Cron; admin settings show WP-Cron status and pending job count
• Improve async translation settings UI: explicit on/off toggle with WP-Cron health indicator

1.1.19

• Fix custom HTML blocks (wp:html) not being protected on large posts — replaced fragile regex with strpos-based scanner; now works regardless of block content size

1.1.18

• Skip translation of custom HTML blocks (wp:html), embed blocks (wp:embed), code blocks (wp:code) and preformatted blocks (wp:preformatted) — their inner content is now preserved verbatim and never sent to the translation API

1.1.17

• Fix Elementor hook firing for free users — elementor/document/after_save is now gated on premium, preventing unwanted API calls on free installs

1.1.7

• WordPress.org compliance: remove premium license gating — all features (page builders, SEO, ACF, WooCommerce) are now fully available without a license
• Convert inline <script> and <style> tags to wp_enqueue_script() / wp_enqueue_style() / wp_add_inline_script() / wp_add_inline_style()
• Fix ACF options key prefix: options_ → pdt_acf_ to avoid collision with global namespace
• Set Freemius is_premium => false and is_org_compliant => true for WP.org compliance
• Rename plugin: « AutoLingo — Translation for Polylang » (remove DeepL trademark from name)

1.1.6

• Fix shortcode and SEO-variable protection not applying when Google Translate or OpenAI is the active provider — protection is now applied universally in the translation wrapper

1.1.5

• Add module toggle checkboxes in settings for page builders, SEO, ACF, and WooCommerce
• Settings page: module checkboxes now saved per-option (pdt_module_*)
• Docs (EN + FR): two-card pricing section, updated hero and FAQ

1.1.4

• Resolve all WordPress Plugin Check issues for WordPress.org submission
• Fix wp_redirect → wp_safe_redirect in manual translate handler
• Add ABSPATH guard to CLI file
• Escape all dynamic output (CSS vars, numeric values) throughout admin pages
• Gate all error_log() calls on WP_DEBUG_LOG
• Remove load_plugin_textdomain() (auto-loaded since WordPress 4.6)
• Integration tests now save and restore source/target language settings

1.1.3

• Fix SEO meta (Yoast, RankMath, SEOPress) not re-translating when updated independently from post content

1.1.2

• Fix Elementor Flexbox Container (v4+) translation — atomic $$type format now handled

1.1.1

• Rebranded to AutoLingo — slug renamed to autolingo-polylang-translate, Plugin URI updated to auto-lingo.com
• Multi-provider architecture — DeepL, Google Translate, and OpenAI share a common provider interface

1.1.0

Bug fixes
* Polylang language not correctly assigned to the translated post after creation
* DeepL HTTP 400 on complex Gutenberg content — resolved by wrapping in a <div>
* ACF url and email field types are no longer sent to DeepL
* Polylang internal taxonomies excluded from term sync
* Admin notices now use transients instead of GET parameters (security fix)

Page builders
* Elementor — widget settings translated via _elementor_data
* Beaver Builder — module settings translated via _fl_builder_data; global nodes skipped
* Bricks Builder — elements and nested items translated via _bricks_page_content_2
* Shortcode protection for Divi, WPBakery, Flatsome, Contact Form 7

SEO
* Yoast SEO, RankMath, SEOPress, The SEO Framework meta fields translated
* SEO template variables preserved via <span translate="no">

WooCommerce
* Custom product attributes translated (name + pipe-separated values)
* Purchase note (_purchase_note) translated
* Price, stock, SKU excluded from meta copy

Technical
* Automatic post meta copy on translation creation
* DeepL HTTP 429 retry with exponential back-off (2 s → 4 s → 8 s)
* Integration test suite: 18 tests covering all modules
* Full i18n — French (fr_FR) translation included
* Freemius SDK integrated for license management

1.0.0

• Initial release