[WordPress] 外掛分享: AutoLingo — Translation for Polylang

首頁外掛目錄 › AutoLingo — Translation for Polylang
WordPress 外掛 AutoLingo — Translation for Polylang 的封面圖片
全新外掛
安裝啟用
尚無評分
9 天前
最後更新
問題解決
WordPress 6.0+ PHP 8.0+ v1.1.17 上架:2026-06-25

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.1.17) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「AutoLingo — Translation for Polylang」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

AutoLingo connects your Polylang-powered site to DeepL, Google Translate, or OpenAI and automates the entire translation workflow — from a single post to your full content library.
Features

Translate Gutenberg content (title, blocks, excerpt) on publish or manually
Manual translate button in the post editor and post list
Bulk translation via WP-CLI (translate-missing, translate-all)
DeepL Free and Pro plan auto-detection (key suffix :fx)
Credit balance check before each translation
Admin alert + dashboard widget when credit runs low
Translated category and tag sync via Polylang
Post meta copy on creation (theme settings, page templates, layout options)
Page builder support: Elementor, Beaver Builder, Bricks Builder
SEO meta translation: Yoast SEO, RankMath, SEOPress, The SEO Framework
ACF field translation: text, textarea, wysiwyg, link, repeater, flexible content
WooCommerce: custom product attributes and purchase note

Page builder support

Elementor — _elementor_data (JSON), all common widget types
Beaver Builder — _fl_builder_data (serialized PHP), global nodes skipped
Bricks Builder — _bricks_page_content_2 (JSON), nested items (accordion, tabs)
Divi / WPBakery / Flatsome — shortcodes preserved verbatim

SEO plugin support

Yoast SEO — title, meta description, focus keyword
RankMath — title, description, focus keyword
SEOPress — title, description
The SEO Framework — title, description
SEO template variables (%%title%%, %sep%, %sitename%…) are preserved automatically

ACF
Translates text, textarea, wysiwyg, and link (title only) fields, including repeater and flexible_content layouts.
WooCommerce
Translates custom product attributes (name + pipe-separated values) and the purchase note. Price, stock, and SKU are never modified.
Reliability

Exponential back-off retry on HTTP 429 (rate limit): 2 s → 4 s → 8 s, up to 3 retries
Dual lock (static + transient) prevents duplicate translations on Gutenberg REST saves
Translation log viewer in the admin (DB-backed, 30-day retention)
Integration test suite — 30 tests covering all modules

External Services
This plugin optionally connects to one of three external translation APIs depending on which provider you choose in Settings → AutoLingo. No data is ever sent without an explicit translation action and a valid API key that you supply yourself.
DeepL
What it is: DeepL is a machine translation service. This plugin uses the DeepL REST API to translate your post content.
What data is sent: The text content of your posts (title, body, excerpt) is sent to DeepL’s servers for translation. If you use the Glossary feature, your glossary terms (source and target words) are also sent to create a DeepL glossary. No personally identifiable information about your site visitors is transmitted.
When it is sent: Only when a translation is triggered — either manually via the Translate button, automatically on publish (if enabled in settings), via WP-CLI, or when syncing a glossary.
Service endpoint: api.deepl.com (Pro) or api-free.deepl.com (Free plan)

Terms of Service: https://www.deepl.com/legal/terms
Privacy Policy: https://www.deepl.com/privacy

OpenAI
What it is: OpenAI provides the GPT language model API. This plugin uses the gpt-4o-mini model to translate your post content when OpenAI is selected as the provider.
What data is sent: The text content of your posts is sent to OpenAI’s servers. No visitor data is transmitted.
When it is sent: Only when a translation is triggered manually or on publish.
Service endpoint: api.openai.com

Terms of Service: https://openai.com/policies/terms-of-use
Privacy Policy: https://openai.com/policies/privacy-policy

Google Cloud Translation
What it is: Google Cloud Translation API provides machine translation. This plugin uses it to translate post content when Google Translate is selected as the provider.
What data is sent: The text content of your posts is sent to Google’s servers. No visitor data is transmitted.
When it is sent: Only when a translation is triggered manually or on publish.
Service endpoint: translation.googleapis.com

Terms of Service: https://cloud.google.com/terms
Privacy Policy: https://policies.google.com/privacy

Configuration

Get a DeepL API key at deepl.com

Free plan — 500,000 characters/month, key ends with :fx
Pro plan — pay-as-you-go

Enter the key under Settings → AutoLingo
Choose your source language (default: French) and target languages (default: English)
Choose which content types to translate (default: Posts and Pages)

WP-CLI Commands
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

延伸相關外掛

文章
Filter
Apply Filters
Mastodon