AIT Multilingual Translate
| 开发者 | itdesignsro |
|---|---|
| 更新时间 | 2026年7月3日 21:31 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
AIT Multilingual Translate helps site owners translate WordPress content with AI and machine translation providers while saving translations locally for reuse.
The plugin is currently available as a Public Beta Build. Please make a backup before bulk translating production websites.
Language flag icons are bundled locally from the MIT-licensed lipis/flag-icons project. No external request is made to load flag images.
Key features
- Select source and target languages.
- Translate with OpenAI, Google Translate, DeepL, Gemini, or Grok/xAI.
- Choose a global Translation Mode / Tone of Voice for AI providers such as SEO Optimized, Marketing, eCommerce, Technical, Legal, Luxury Brand, Friendly, or Custom Prompt.
- Use AI Cost Optimization settings for Cheap, Balanced, or Premium model guidance, temperature control, request limits, token estimates, cache hits, and duplicate-skipped statistics.
- Store translations locally and reuse them until source text changes.
- Scan posts, pages, products, menus, widgets, taxonomy terms, SEO meta, and public custom fields.
- Process translation work in a queue so visitors do not wait for provider calls.
- Edit saved translations from the frontend as an administrator.
- Manage translations in a searchable Translation Matrix.
- Export and import translations as CSV, PO, or MO files.
- Add language switchers with shortcodes, widgets, Elementor, WordPress menus, header, or footer placement.
- Use directory URLs such as
/ka/about/or query URLs such as/about/?lang=ka. - Includes WooCommerce product and category URL compatibility helpers.
- Includes a debugger, route diagnostics, safe log export, and provider test tools.
wp-config.php.
Trademark notice
WooCommerce and Elementor are trademarks of their respective owners. This plugin is not affiliated with, endorsed by, or sponsored by WooCommerce, Automattic, Elementor, or their parent companies.
External services
AIT Multilingual Translate can connect to external translation providers. No provider is contacted unless you configure a provider key and start a provider test, queue process, background queue run, or on-page translation request.
For all providers, the plugin may send source text strings, source language, target language, provider model/endpoint selection, and request metadata required by the provider. API keys are sent only to the selected provider endpoint and are not shown in the debugger or public output.
OpenAI:
- Sends selected strings and language instructions to OpenAI when OpenAI is the active provider.
- Terms: https://openai.com/policies/terms-of-use/
- Privacy: https://openai.com/policies/privacy-policy/
- Google Translate is used to translate selected source strings when Google Translate is selected as the active provider and the site owner has configured a Google Cloud Translation API key.
- The plugin sends source text strings, source language and target language to Google Cloud Translation API only when the site owner starts a provider test, queue process, background queue run or on-page translation request.
- Terms: https://cloud.google.com/terms
- Privacy: https://policies.google.com/privacy
- Sends selected strings plus source and target language codes to DeepL when DeepL is the active provider.
- Terms: https://www.deepl.com/pro-license
- Privacy: https://www.deepl.com/privacy
- Sends selected strings and language instructions to the Gemini API when Gemini is the active provider.
- Terms: https://ai.google.dev/gemini-api/terms
- Privacy: https://policies.google.com/privacy
- Sends selected strings and language instructions to xAI when Grok/xAI is the active provider.
- Terms: https://x.ai/legal/terms-of-service
- Privacy: https://x.ai/legal/privacy-policy
安装:
- Upload the
ait-multilingual-translatefolder to/wp-content/plugins/or install the ZIP through Plugins > Add New > Upload Plugin. - Activate AIT Multilingual Translate.
- Open AI Translate in the WordPress admin menu.
- Choose source and target languages.
- Select a provider and add the provider API key.
- Run the scanner to collect site strings.
- Process the translation queue.
- Add a language switcher using
[aitmt_language_switcher], a widget, Elementor, or a WordPress menu item.
屏幕截图:
常见问题:
Does AIT Multilingual Translate translate pages on every visit?
No. The recommended workflow is to scan strings, process them in the queue, save translations locally, and serve saved translations to visitors.
Can I use the plugin without an AI provider?
Yes. You can scan strings and manually edit translations in the Translation Matrix. Provider translation requires a provider API key.
Does the plugin support WooCommerce?
The Public Beta Build includes WooCommerce product and product-category URL compatibility helpers and scanner coverage for product content. Always test stores on staging before bulk translation.
Where are translations stored?
Translations are stored in a custom WordPress database table named with the site prefix, usually wp_aitmt_translations.
Are API keys visible in logs?
The debugger masks provider keys. Safe debug exports redact secrets and sensitive data before inclusion in reports.
Can I define API keys in wp-config.php?
Yes. Supported constants are AITMT_OPENAI_API_KEY, AITMT_GEMINI_API_KEY, AITMT_GROK_API_KEY, AITMT_GOOGLE_TRANSLATE_API_KEY, and AITMT_DEEPL_API_KEY.
更新日志:
0.3.39
- Added safe-by-default provider pricing notices, setup assistants, quota/budget guidance, and API cost estimator UI.
- Changed new-install defaults to conservative plugin-side character limits, smaller batches, and disabled background/page-load translation behavior.
- Improved target-language search so language codes such as
rumatch the correct language.
- Clarified queue source reporting by separating queued characters from historical total characters.
- Added a guarded page-load queue cleanup action for sites where page-load collection was previously enabled.
- Added a production warning when page-load collection is enabled.
- Added a guarded cleanup action for technical/non-translatable queued rows such as data URIs, base64 payloads, URLs, hashes, IDs, JSON/settings data, asset paths, and code fragments.
- Added skipped-string diagnostics with top rejection reasons and technical samples.
- Blocked Translate All when queued rows contain unknown or technical/non-translatable items.
- Improved Translate All estimates with blocked technical rows/characters separated from billable unique source strings and target-language jobs.
- Added unsafe page-load guards for customizer, Elementor preview, WooCommerce cart/checkout/add-to-cart/remove-item, filter, sort, and preview requests.
- Prevented source_type=unknown rows from being created when source metadata cannot be determined.
- Blocked unsafe
source_type=unknownqueued rows from provider processing. - Added a Queue Debug Report with top source types, object IDs, field keys, target-language counts, duplicate hashes, and longest queued strings.
- Added a guarded cleanup action for queued rows with missing/unknown source metadata.
- Improved Translate All estimates to separate total queued rows, unique source strings, target-language jobs, billable characters, and per-language character totals.
- Tightened scanner guards for technical strings, JSON/settings data, classes, URLs, hashes, short values, and oversized strings.
- Added queue lock and processing status safeguards for translation batches.
- Added retry limits and failed status for problematic queued translations.
- Added Translate All cost estimate and explicit confirmation before bulk processing.
- Added provider usage logging and source reporting for queued translations.
- Changed new-install defaults so page-load translation, background processing, and scan-on-save stay disabled until explicitly enabled.
- Narrowed Elementor scanning to visible human-readable fields.
- Added Google Cloud Translation API billing warning and safer local quota defaults.
- Updated DeepL Terms and Privacy Policy URLs in readme.txt for WordPress.org review.
- Renamed public plugin branding to AIT Multilingual Translate.
- Removed WordPress.org restricted/trademark-sensitive wording from the public plugin name.
- Reworked internal prefixing from wpait/WPAIT toward aitmt/AITMT naming.
- Removed custom updater / self-update override logic for WordPress.org compliance.
- Improved WordPress enqueue handling for JavaScript and CSS.
- Improved external services disclosure in readme.txt.
- Removed or corrected broken external service legal/privacy links.
- Improved plugin directory/path handling using WordPress helper functions.
- Improved output buffering lifecycle.
- Improved output escaping in frontend/admin rendering.
- Restored target language search in the dashboard and setup wizard after the public prefix cleanup.
- Restored frontend language switcher styling for shortcode, Elementor widget, automatic placement, and WordPress menu output.
- Restored frontend editor editable text detection and AJAX actions after the final
aitmtprefix rename. - Tested the updated package with Plugin Check.
- Prepared updated ZIP package for WordPress.org review.
- Renamed the final WordPress.org submission package to AIT Multilingual Translate.
- Updated the plugin slug, folder, ZIP name, and text domain to
ait-multilingual-translate. - Removed beta self-update/repair updater hooks for WordPress.org compliance.
- Updated external-services disclosure and generated log directory handling.
- Added explicit output-buffer shutdown handling for review safety.
- Renamed the public WordPress.org plugin name to AIT Multilingual Translate.
- Updated the submission slug and package root to
ait-multilingual-translate. - Updated the text domain and language template filename for WordPress.org language-pack readiness.
- Updated public-facing branding, readme text, and WordPress.org trademark wording.
- Kept internal prefixes, option names, database tables, shortcodes, translation engine, queue, scanner, routing, Elementor widget, frontend editor, and WooCommerce compatibility logic unchanged.
- Added AI Cost Optimization settings for quality mode, temperature, request character limits, estimated per-request cost limits, model guidance, and token/cost statistics.
- Added safe deduplication before provider requests and translation-memory cache-hit handling for frontend auto-translate.
- Added provider capability cards for active providers and planned architecture targets without enabling unfinished provider API integrations.
- Loaded the WordPress text domain for language-pack readiness and disabled the older internal dictionary fallback.
- Updated the public package slug to
ait-multilingual-translate. - Kept translation engine, queue architecture, scanner collection logic, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.
- Finalized the Translation Style / Tone of Voice settings section for the Public Beta release.
- Added Translation Mode visibility to Scanner and Queue statistics.
- Documented that per content type modes are planned for a future release while the current build uses Global Translation Mode.
- Kept translation engine, queue architecture, scanner collection logic, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.
- Added a Scanner and Queue "Translate All" action that processes queued translations in safe provider batches with quota/time-limit guidance.
- Finalized Global Translation Mode / Tone of Voice UI copy and server-side custom instruction length protection.
- Kept translation engine, queue architecture, scanner collection logic, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.
- Fixed admin asset loading for all plugin subpages after the public slug change.
- Replaced the remaining public Elementor switcher label that used a previous public label.
- Updated the modular settings link to the new top-level admin page.
- Kept translation engine, queue, scanner, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.
- Prepared the public WordPress.org package name, metadata, and build structure for AIT Multilingual Translate.
- Added Translation Mode / Tone of Voice settings for prompt-based AI providers.
- Switched default OpenAI model to
gpt-4o-miniand Grok default to a lightweight model where available. - Hardened custom-table SQL and local file handling for WordPress.org Plugin Check compatibility.
- Kept translation engine, queue, scanner, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.
- Added secure frontend editor Auto Translate so administrators can request an AI/provider translation inside the edit modal, review it, and save manually.
- Improved frontend editor modal loading state, textarea auto-resize, mobile spacing, and provider error messaging.
- Kept translation engine, queue, scanner, routing, WooCommerce handling, translation matrix, and language switcher behavior unchanged.
- Replaced remaining
parse_url()calls with WordPresswp_parse_url()for Plugin Check compatibility. - Added translator comments and documented safe internal HTML output paths.
- Improved uninstall variable prefixing for WordPress Coding Standards.
- Kept translation engine, queue, scanner, routing, WooCommerce handling, and language switcher behavior unchanged.
- Public Beta Build prepared for WordPress.org submission.
- Added WordPress.org
readme.txt. - Added GPL license file and plugin header license metadata.
- Replaced earlier beta wording with "Public Beta Build".
- Hardened uninstall table-name handling.
- Preserved translation engine, queue processing, scanner, routing, provider logic, frontend editor, WooCommerce compatibility, Elementor widget logic, and language switcher core logic.
- Added menu language switcher anchor protection for themes that rewrite menu links.
- Prevented the frontend language URL rewriter from overwriting WordPress menu language switcher links.
- Improved menu language switcher behavior for current-language switcher items.