Transleti Translator -- WordPress 插件

开发者	transleti grupobouso
更新时间	2026年7月20日 08:40
PHP版本:	8.0 及以上
WordPress版本:	7.0
版权:	GPLv2 or later
版权网址:	版权信息

The plugin is 100% free and GPL. You can run a fully multilingual WordPress site with manual translations, hreflang sitemap, language switcher and slug translation without ever paying anything or connecting to an external service. If you also want automatic translation across every language at once, connect the optional Transleti API — flat-rate, unlimited words and languages, backed by a 14-day money-back guarantee. The API is optional: the manual workflow keeps working forever, even if you never subscribe. Transleti Translator handles posts, pages, custom post types, WooCommerce products, menus, slugs, SEO meta, and theme strings. A built-in visual editor lets you click on any text in the rendered page and refine its translation in a side-by-side panel — useful both for polishing automatic translations and for translating everything by hand. Two ways to use it

Manual mode (free, forever) — edit each translation directly in the WordPress post editor or via the visual front-end editor. No API key, no subscription, no external connection required. Includes the language switcher, hreflang sitemap, slug translation and 49+ pre-defined language slots.
Automatic mode (optional Transleti API) — connect an API key and the plugin fans out translations to every target language in parallel. Flat-rate, unlimited words, with a 14-day money-back guarantee. If you decide to stop, the plugin keeps working in manual mode. Manual edits on top of automatic translations are preserved on re-translation.

Features

Free GPL plugin — fully functional in manual mode without any external connection or paid service.
Visual translation editor — open any front-end page in an editor frame, click on any string (titles, paragraphs, menu items, buttons, image alts) and edit its translation in a side panel with live preview.
Manual translation editor — review and refine translations directly in the WordPress post editor for every language.
Optional unlimited automatic translation — flat-rate Transleti API subscription with a 14-day money-back guarantee. If you do not keep the subscription, the API stops and the plugin keeps working in manual mode.
Parallel translation (API mode) — requests fan out to every target language simultaneously. A site with 10 languages translates in roughly the same time as a site with 1.
Built on open source — the plugin itself is GPL, fully auditable, no proprietary lock-in.
Theme & builder-agnostic — works out of the box with Elementor, Divi, Gutenberg, classic editor, GeneratePress and any standards-compliant theme.
WooCommerce ready — translates product titles, descriptions, attributes and variations (with WooCommerce Multilingual & Multicurrency when running in WPML Connector Mode).
WPML Connector Mode — already using WPML? Keep WPML in charge of your languages, URLs, switcher and stored translations, and let Transleti act purely as the automatic translation engine behind it. Detected and enabled automatically; no double language switching or duplicate URLs.

Key features

Multilingual sitemap with hreflang — separate <url> entries per language (the format Google explicitly documents) with self-referential hreflang and x-default. Compatible with Yoast SEO, RankMath, SEOPress, AIOSEO and the WordPress core sitemap.
SEO meta translation — titles and descriptions for SEOPress, Yoast, AIOSEO and RankMath.
Visual translation editor — open any front-end page in an editor frame, click on any string (titles, paragraphs, menu items, buttons, image alts) and edit its translation in a side panel with live preview.
Manual translation editor — review and refine translations directly in the WordPress post editor for every language.
Manual edit protection — your manual fixes survive re-translation cycles.
Slug translation — translated URLs (e.g. /es/contacto/) for clean per-language SEO.
Menu translation — duplicates and translates navigation menus per language.
HTML entity and shortcode protection — prevents corruption of ©, [shortcode], and similar in translated output.
Custom "do not translate" word list — keep brand names, product codes and acronyms intact across all languages.
Language switcher — widget, block and shortcode in flag, dropdown or text styles.

Supported languages 49+ languages including English, Spanish, French, German, Italian, Portuguese (PT/BR), Dutch, Polish, Romanian, Bulgarian, Hungarian, Finnish, Russian, Ukrainian, Arabic, Hindi, Japanese, Korean, Chinese, Thai, Turkish, and more. How it works Manual mode (free):

Install and activate the plugin.
Choose your default language and the target languages you want to publish.
For each post / page, open the translation editor (in the post editor sidebar or via the visual front-end editor) and type the translation by hand.
The language switcher, hreflang sitemap and per-language slugs work out of the box.

Automatic mode (optional API):

Install and activate the plugin.
Sign up at https://transleti.com to get your API key (flat-rate subscription with a 14-day money-back guarantee).
Enter your Transleti API key in the plugin settings.
Choose your default language and the languages you want to publish.
The plugin runs a background job that translates posts, menus, slugs and SEO meta automatically.
Optionally refine any translation manually from the WordPress post editor — your edits are preserved on re-translation.

1.9.38

New: WPML Connector Mode. If WPML is active, the plugin now detects it and works as WPML's automatic translation engine instead of managing languages itself. WPML keeps full control of your languages, URLs, switcher and stored translations, so there is no conflict, no duplicate switcher and no duplicate URLs. It translates posts, pages, custom post types, taxonomy terms, menus, slugs, SEO meta and interface strings into every WPML language. Enabled automatically; you can force plain Standalone mode from the new Connector tab. Sites without WPML are unaffected and keep running exactly as before.
New: WooCommerce + WPML support. With WooCommerce Multilingual & Multicurrency (WCML) installed, products, categories and tags are translated automatically, and each shop page correctly shows only the products for the language being viewed (no more all-languages product lists). A translated product stays blocked with a temporary notice until its title and description are ready, so shoppers never see a half-translated page.
New: form fields (SureForms) are now translated per language, including placeholder text, instead of falling back to another language.
Fix: a newly added language no longer stays stuck behind the "translation in progress" page — the readiness check now ignores strings that are handled elsewhere, so the language goes live as soon as its content is done.
Change: the automatic translation API is now a flat-rate subscription with a 14-day money-back guarantee (the previous 7-day trial has been retired). The plugin remains free and fully usable in manual mode.

1.9.37

Fix: corrections made in the visual (in-page) translation editor now reliably apply. Previously, editing some text directly on an already-translated page could save your change against the wrong entry and appear to do nothing; the editor now matches the edit to the correct source string and updates it.

1.9.36

Fix: per-language progress now reaches 100% correctly. Entries that were intentionally set aside — untranslatable strings and text detected as belonging to another language — no longer hold the bar below 100%, since there is no further work to do on them.
Fix: extended the cross-language cleanup so text already stored in a wrong language (including entries produced by earlier versions) is removed even after it was translated, across both the page and interface string stores. Legitimate labels that mix a few foreign characters with your own language (for example a place name written as "Beijing / 北京") are always kept.

1.9.35

Fix: much stronger protection against one language's text mixing into another. Text that your theme or plugin already displayed in the visitor's language is now reliably detected and never re-translated or copied to other languages — including European (Latin-script) languages that earlier checks could not catch — so it simply shows in that language as intended. This runs automatically and cleans up any entries that had already accumulated.
Fix: a translation that comes back with characters from the wrong writing system (for example a few stray characters from another alphabet mixed into an otherwise correct result) is now rejected and translated again cleanly, instead of being stored. Your original content is never modified.
Fix: brand names such as "WordPress" and "WooCommerce" are now kept intact in every language, including scripts where some engines previously mangled or truncated them (e.g. Thai dropping the final letter). A protected brand that a low-resource model corrupts mid-translation is now recovered automatically instead of leaking a placeholder.
New: the language switcher's country flags now load a bundled flag font, so they render on platforms whose system fonts omit flag emoji (Windows and some Linux) instead of showing empty boxes or letters. Scoped to flag characters only; can be turned off with the transleti_load_flag_font filter.

1.9.34

New: pages translated into a language whose script your theme font doesn't cover (Hindi and other Indic scripts, Chinese, Japanese, Korean, Arabic, Hebrew, Thai and more) now automatically load a matching high-quality webfont, so the text is fully readable instead of showing empty boxes. Latin, Greek and Cyrillic languages are left untouched, icon fonts are preserved, and it can be turned off with the transleti_load_webfonts filter.

1.9.33

Fix: prevents translations from one language leaking into another. When a theme or plugin displayed text that was already in a different language (for example a native navigation menu or shop labels), earlier versions could mistake it for source text and copy it into every language, creating a few wrong or foreign-looking entries and wasting translation quota. Such text is now ignored when detected and never copied between languages, and any entries that had already accumulated are cleared automatically when you update. Your original content is never modified.

1.9.32

Change: automatic translations created during the 7-day free trial are now cleared if the trial ends without starting a subscription. This only affects trials that end unpaid — once you have made at least one payment, your translations always stay in your own site and keep working for free, even after a cancellation (see the "Who owns the translations" FAQ). Your original content is never modified.

1.9.31

Fix: a page whose SEO title or description can't be machine-translated into a particular language (e.g. a brand-only or malformed title) no longer retries forever or stays flagged as "blocked" — after a few attempts the page is finalized with the source-language text for that string, the same graceful give-up already used for individual dictionary entries.
Fix: the "translations blocked for over an hour" notice and its email digest no longer list internal, non-public post types (e.g. WooCommerce support-ticket messages); stale entries are cleaned up automatically and remaining ones are labelled clearly even when the item has no title.

1.9.30

Improvement: when the higher-quality home and SEO translation is temporarily unavailable, the translated home page is now held on the friendly "translation pending" page instead of being shown at lower machine-translation quality — so visitors and search engines never see a lower-quality home. It restores automatically as soon as the higher-quality translation is ready.

1.9.29

Improvement: higher-quality automatic translation of the home page and its SEO fields (page title, meta description and navigation menus), for a stronger first impression and better search-engine and social previews on translated pages.
Fix: secondary languages could get stuck below 100%. Strings discovered while rendering one language are now propagated to every active language automatically, so low-traffic languages no longer lag behind; the per-language progress indicator is also more robust when one language happens to carry extra strings.
Fix: internal, non-public post types (for example WooCommerce support-ticket messages) are no longer reported as "stuck" translations or held back by the "translation pending" page — only genuinely public pages are gated and crawled.
Fix: the logged-in admin toolbar is no longer captured as translatable content, keeping per-language string counts and progress accurate.
Fix: navigation menus now translate from the correct source menu, preventing already-translated labels from being re-queued into the wrong language.
Fix: duplicate dictionary entries for the same source string are de-duplicated, so a stray automatic translation can no longer shadow a better one (menus and home strings render correctly).

1.9.28

Fix: one-time recovery of SEO titles, descriptions and other strings that were left in the source language after an earlier translation-engine outage. Before 1.9.27 a connection timeout could permanently flag pending strings as failed; those rows stayed excluded from the queue even after the engine recovered. On upgrade the plugin now requeues them automatically (runs once), so previously stuck translations complete on the next translation cycles. No action required.
Fix: API keys, JWT auth tokens and hash/digest strings (e.g. on account or API-key pages) are no longer queued for translation. They were never translatable, so the engine kept rejecting them and they piled up in the pending list. They are now detected and stored as-is, keeping the queue and the "pending strings" notice clean. Guarded so real text — including non-Latin scripts — is never affected.

1.9.27

Fix: on translated pages the <title> could render empty and <html lang> could stay on the default language when an SEO plugin (e.g. Rank Math) built the document head before the language context was active. The output buffer now rewrites <html lang> to the current language and rebuilds an empty/missing <title> from the translated title, so search engines never see a blank title on a translated page.
Fix: fatal TypeError in the Rank Math sitemap integration (rankmath_sitemap_url() received an array, not a string) that could break the Rank Math sitemap and its hreflang alternates. The handler now accepts both, matching the SEOPress integration.
Fix: the 503 "translation pending" page could fatal (and serve a raw 503 error instead of the friendly template) when triggered from the render layer, because it started a new output buffer inside the page output buffer. The pending page is now built as a string and renders correctly in every context.
Fix: a temporary translation-engine outage (connection timeout or server error) no longer counts against a string's retry limit. Previously a few minutes of downtime could permanently flag pending strings as failed, leaving them in the source language even after the engine recovered. Transient failures are now retried indefinitely; only genuine per-string rejections count toward the limit.
Fix: hardened the background translator against a missing source-language setting that could throw a fatal error on every cron run and silently stop all translation; it now falls back to the default source language.

1.9.26

Doc: improved the WordPress.org listing title, tags and short description for better discoverability (no functional changes).

1.9.25

SEO: the real composite page title (Post - Site - Tagline), og:title and meta description are now fetched from the rendered page and translated proactively in the background batch, before the first visit — so search engines and social previews never see an English title on a translated page. A render-side gate holds a secondary-language page at 503 while its <title> is still untranslated, with a fail-open grace period so a title that never translates can't strand the page.
Fix: homepage redirect loop on sites served over both www and non-www. Automatic language detection now reads the visitor's current language from a host-agnostic signal instead of the rewritten request URI, so www. secondary-language pages no longer bounce in a redirect loop.
Fix: cookie-consent notice mistranslated in Urdu (ur) — the translation engine rendered "cookies" as پکوان ("food dishes"). A per-language term lock now forces the correct word (کوکیز) so the notice translates correctly, with a safeguard that falls back cleanly if the engine corrupts the protected term.

1.9.24

UI: fixed vertical alignment of dashicons inside admin buttons on the plugin settings page.
Doc: refreshed screenshots and captions for every plugin tab on the WordPress.org listing.

1.9.23

Fix: WooCommerce Blocks cart / checkout — product short descriptions now translate correctly. WC Blocks pre-renders the cart server-side via a hydration path that bypasses the REST response filter; the plugin now hooks woocommerce_hydration_request_after_callbacks so hydrated responses are translated alongside live Store API calls.
Fix: WooCommerce Blocks Summary truncation — product short descriptions in cart / checkout are no longer clipped to ~15 characters on locales whose WordPress translation breaks the Word count type. Do not translate! hint (e.g. pt_BR returning "palavras"). Both the server-side _x() value and the client-side wp.i18n translation file entry are now sanitised back to a valid value.
Fix: Store API translation — WC Blocks calls /wc/store/v1/* without a language URL prefix from the localized React bundle. The plugin now falls back to HTTP_REFERER to detect the visitor's current language so Store API responses match the page they were requested from.
Doc: readme repositioned to make clear the plugin is free and fully usable in manual mode; the Transleti API (automatic translation) is now described as optional.
Doc: trial messaging updated to reflect that the 7-day API trial no longer requires a card or payment method. After the trial, the API stops automatically unless you subscribe and the plugin keeps working in manual mode for free.

1.9.22

Fix: per-language progress no longer gets stuck below 100% on mixed-script content. Dictionary rows now retire after 3 failed translation attempts (mirroring the existing gettext mechanism), so untranslatable strings stop blocking the percentage indicator.

1.9.21

Fix: visual editor — clicks on theme menu items (GeneratePress, Astra, Divi, Elementor Pro mega-menus, etc.) now open the translation panel reliably. Listener moved to window capture + pointerdown so theme menu togglers that call stopPropagation() can no longer swallow the selection click.

1.9.20

Fix: visual editor now detects menu items in Hebrew, Greek, Hindi, Thai, Georgian and Armenian (menu translation now bails during preview so the renderer can add translatable markers regardless of script).
Fix: visual editor — clicking on a string with duplicated text on the same page (e.g. a heading and a menu link with the same label) now opens the translation panel for the selected occurrence.
Fix: ignore RSS feed pubDate/lastBuildDate strings in the "stuck translations" notice.
Improvement: automatic cleanup of orphan sentence segments left over from long-paragraph batching.

1.9.x

New: visual translation editor — click any text in the rendered front-end and edit its translation in a live side panel. Works on menus, buttons, image alts and theme strings.
New: 49+ languages supported via the Transleti translation API.
New: HTML entity and shortcode protection across all translation entry points.
New: "Do not translate" word list (brand names, product codes, acronyms).
New: SEO meta translation for SEOPress, Yoast, AIOSEO and RankMath.
Improvement: manual edit protection — your manual fixes survive re-translation cycles.
Improvement: parallel translation across all target languages.

1.4.4

Feature: drag-and-drop reordering of active languages in the Languages tab (also affects the language switcher order).
i18n: added 503 "pending translation" page strings for 16 additional languages (Lithuanian, Albanian, Azerbaijani, Basque, Bengali, Catalan, Esperanto, Galician, Irish, Kyrgyz, Latvian, Malay, Persian, Slovenian, Tagalog, Urdu).

1.4.3

Compliance: wrapped language_has_translations() and find_original_slug() direct $wpdb probes with wp_cache_get / wp_cache_set (5-minute TTL, transleti cache group).
Compliance: documented every legitimate direct DB call against core meta tables with phpcs:ignore comments explaining why the existing core API can't replace them.

1.4.2

Hardening: escaped flag-emoji output in the language switcher shortcode (render_switcher, render_language_list) via esc_html().
Hardening: every ob_start() callback buffer is now explicitly closed via a paired ob_end_flush() registered through register_shutdown_function() in the same function scope (frontend page buffer, AJAX response buffer, sitemap xhtml-namespace buffer).

1.2.1

Hardening: replaced fopen/fread/fclose with WP_Filesystem::get_contents() for the diagnostic log reader.
Hardening: switched all custom-table existence checks to $wpdb->prepare( 'SHOW TABLES LIKE %s', ... ) (no more single-quote interpolation).
Hardening: switched several $_POST reads on HTML-bearing fields to wp_kses_post( wp_unslash( ... ) ); integer reads now use absint( wp_unslash( ... ) ).
Hardening: added explicit nonce checks (check_admin_referer/wp_nonce_url) to the string-export download link.
Compliance: removed redundant load_plugin_textdomain() call (WP 4.6+ auto-loads translations from the WP.org directory).
Compliance: documented every legitimate direct-DB query (custom plugin tables) with localised phpcs:disable/enable blocks.

1.2.0

Compliance: removed comparative/superlative marketing phrasing from the readme.
Compliance: extracted inline <script> blocks to enqueued JS files (language switcher, editor preview).
Hardening: all $_GET / $_POST / $_SERVER / $_COOKIE reads now go through wp_unslash() plus a context-appropriate sanitiser (sanitize_text_field, esc_url_raw).
Hardening: AJAX nonce check in ajax_empty_language() now unslashes and sanitises the nonce before passing it to wp_verify_nonce().

1.0.6

Removed redundant load_plugin_textdomain() call — translations are now auto-loaded by WordPress 4.6+ for plugins hosted in the directory.
Switched front-end language redirect from wp_redirect() to wp_safe_redirect() for additional protection against open-redirect attempts.
Defense-in-depth: explicit allowlist validation for the language storage key before SQL identifier interpolation in the cache-clearing endpoint.
Packaging: included a .pot template in languages/ so the Domain Path folder is present in the distributed package.

1.0.5

New: separate <url> entry per language in the sitemap, matching Google's documented hreflang format.
New: AIOSEO sitemap compatibility (aioseo_sitemap_post/_term/_archive_entry/_addl_pages filters).
Fix: xmlns:xhtml namespace now declared in <urlset> so <xhtml:link> alternates are valid XML.
Fix: /sitemap.xml no longer redirects to /en/sitemap.xml when add_subdirectory_to_default=yes.
Fix: sitemap <loc> URLs now use the canonical default-language URL instead of the redirecting unprefixed permalink.
Fix: HTML head and sitemap hreflang codes now match exactly for bidirectional confirmation.

1.0.4

Parallel translation crawling — O(1) in number of languages.
Render substitution fixes for raw %1$s placeholders and [cookie_*] shortcodes leaking to public pages.

1.0.3

HTML entity and shortcode protection in all translation entry points.
"Do Not Translate" word list.
Manual edit protection improvements.

Transleti Translator – Multilingual & Automatic Translation

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: