內容簡介
EffortLess Multisite Auto Translate 是一款專為 WordPress Multisite 設計的外掛，能夠自動將一個網站的文章、頁面及自訂文章類型翻譯並更新到網路中其他選定的網站，提升多語言內容管理的效率。
【主要功能】
• 自動翻譯文章標題和內容
• 支援多種翻譯提供者（OpenAI、DeepL）
• 保留 Gutenberg 區塊結構與屬性
• 可設定翻譯術語的固定翻譯
• 支援網路管理員進行設定
外掛標籤
開發者團隊
② 後台搜尋「EffortLess Multisite Auto Translate」→ 直接安裝（推薦）
📦 歷史版本下載
原文外掛簡介
EffortLess Multisite Auto Translate is a Network-Activated plugin for WordPress Multisite. When a post, page, or custom post type is published or updated on one site in the network (the “source” site), the plugin sends its title, content, categories, and tags to your chosen translation provider (OpenAI or DeepL) and creates or updates a matching translated copy on each of the network’s other sites you’ve selected as a “destination”. Translation runs in the background via WordPress Cron (or Action Scheduler, if another active plugin provides it), not during the page save itself.
Content is translated block by block: each Gutenberg block is sent to the API and reassembled individually, so block structure, attributes, and nested layouts (columns, groups, galleries) survive translation. Shortcodes and core/html blocks are left untouched rather than translated. A Glossary lets you pin specific terms (brand names, proper nouns) to a fixed translation, or to “do not translate,” per destination site if needed.
What gets translated
Post titles and content (Gutenberg blocks)
Pages and public custom post types you haven’t unticked in “Post Types to Translate”
Categories, tags, and other public taxonomies
Post metadata you explicitly add to the “Extra translatable meta keys” setting
What is left untouched
Shortcodes (preserved exactly, including their attributes)
core/html blocks (skipped by default; a elmat_translate_html_block filter exists for developers who want to opt them in)
Private post metadata
Settings (Network Admin → EffortLess Multisite Auto Translate: API configuration, Site configuration and Translation glossary tabs)
Translation Provider — OpenAI (GPT), DeepL, or (WordPress 7.0+ only) the built-in WordPress AI Client, which uses whichever provider your site has configured under Settings → Connectors instead of a key entered here. Only the selected provider’s key below is used.
OpenAI API Key / DeepL API Key — required for whichever provider is selected. A “Test API Key” button verifies the active one before you save.
Enable automatic translations — checkbox. When off, translation only happens if triggered manually from the block editor’s EffortLess Multisite Auto Translate panel.
Publish new translations as draft — checkbox, off by default. When on, a translation’s first creation is saved as a draft instead of published, so a human can review it before it goes live. Only affects first creation — updating an already-published translation keeps updating it in place, never unpublishing it automatically.
GPT Model — gpt-4o-mini (default) or gpt-4o. OpenAI only.
Translation Style — Literal, Natural (default), or Creative — controls how closely the translation sticks to the source wording. Applies to both providers (mapped internally for each).
Additional Instructions — free-text instructions appended to every translation request (tone, formality, house style). OpenAI only — DeepL has no prompt/instruction mechanism.
Post Types to Translate — untick any post type to stop translating it, both automatically and via Bulk Translate. Lists every public post type registered on the source site.
Extra translatable meta keys — a plain-text list (one per line) of additional post-meta keys to translate, for meta fields added by other plugins (e.g. custom SEO title/description fields).
Shared Media Library — optionally designate one site’s Media Library as the single source of truth for images; other sites’ translated content then links back to that site’s files instead of duplicating them.
Source Site — the one site whose saves trigger translation.
Destination Sites — which of the network’s other sites receive translated copies.
Glossary — terms with a fixed translation, so brand names, place names and words with several meanings translate consistently. Pick a language at the top to see and edit its values; a value under “All languages (default)” applies to every language without its own, “Keep as is” leaves a brand name unchanged, and an empty term is left to the AI. It can be exported to a CSV file, edited in a spreadsheet and imported again.
A running character-usage total (this month + lifetime) is shown above the API key fields once translation has run at least once — a rough usage indicator, not exact billing; check your provider’s own dashboard for that.
A “Translation Status” box also appears in the post editor’s sidebar (source site only) showing each destination’s status for the post you’re editing, without a trip to Network Admin.
Tools (Network Admin → EffortLess Multisite Auto Translate → Tools)
Bulk Translate All Posts, Force Re-translate All (clears retry/failure counters and re-sends everything), Sync Design & Templates (switches every destination site’s active theme to match the source, network-enabling it first if needed, then copies global styles, site icon, logo, and queues templates/patterns for translation — a confirmation dialog states the theme change before you proceed), Resync Media Links (also runs automatically whenever the Shared Media Library setting changes), Clean Destinations (removes orphaned translations and non-translation content added directly on a destination site), Flush Permalinks, and Emergency Stop (cancels every pending translation). Stuck queue entries clear themselves automatically within about an hour — there’s no separate cleanup button for that.
Notes and limitations
Requires WordPress Multisite to do anything. It can be installed and activated on a single-site WordPress (for example before you enable Multisite), but there it only shows a notice on the Plugins screen and has no settings. After converting the site to a network, network-activate it from the Network Admin; the one-time network setup runs automatically.
Translated content is saved through WordPress’s normal sanitization; the plugin never disables it. Translations are saved by a background task, as the source post’s author when that author and the user who last saved the source may post unfiltered HTML (on multisite: Super Admins) and the translation adds no code the source lacks. The copy then keeps the source’s