Hybrid AI Translator for TranslatePress
| 开发者 | fmojibur |
|---|---|
| 更新时间 | 2026年8月3日 18:48 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Hybrid AI Translator for TranslatePress registers a new automatic translation engine inside the TranslatePress Multilingual plugin. When a visitor opens a translated URL, this engine automatically translates the page content and TranslatePress caches the result in its own database, so future visits are instant.
Watch the full setup & translation walkthrough:
https://youtu.be/UO3a7TIoNQ8
Official Website | Video Tutorial
How it works
- TranslatePress detects new strings that need translating.
- Our engine sends them to the public Google Translate endpoint (the same endpoint the Chrome browser translate extension uses) and gets back the translated text.
- TranslatePress stores the translation in its database. The next visitor sees the cached translation immediately.
- Google Translate (Unofficial) provider — fast, high quality, no API key needed.
- Configurable timeout, chunk size, and per-request character limit.
- Per-translation log viewer so you can see exactly which strings were translated, when, and how long they took.
- One-click "Test" button to verify connectivity from your server.
- Clean uninstall — all plugin options are removed when you delete the plugin from the WordPress admin.
- This plugin only contacts the translation endpoint you've configured (by default:
translate.googleapis.com). It sends only the strings TranslatePress asks it to translate. - No telemetry, no tracking, no analytics, no calls to any other server.
- No personal data of your visitors is sent anywhere — only the page text that needs translating.
- See the FAQ for the full data flow.
https://translate.googleapis.com/translate_a/single
- What is sent: the source text strings TranslatePress needs translated, plus the source/target language codes.
- When: only when TranslatePress requests a translation for a string that is not yet cached.
- Why: to receive the translated text.
- Provider: Google. Terms: https://policies.google.com/terms. Privacy: https://policies.google.com/privacy. You can change the endpoint URL in the plugin settings if you self-host a compatible service.
安装:
- Install and activate the TranslatePress Multilingual plugin first.
- From your WordPress admin, go to Plugins → Add New, search for "Hybrid AI Translator for TranslatePress", and click Install Now → Activate. (Or upload the plugin ZIP via Plugins → Add New → Upload Plugin.)
- Go to Settings → Hybrid AI Translator and verify the Google provider is enabled. Click Test to confirm your server can reach the endpoint.
- Go to Settings → TranslatePress → Automatic Translation and select "Hybrid AI (Google + Pro AI providers)" as the translation engine, then enable Automatic Translation and Save.
- Visit any translated URL on the front-end. New strings will be translated automatically and cached.
屏幕截图:
常见问题:
Do I need an API key?
No. The Google Translate (Unofficial) provider does not require any API key.
Will Google rate-limit me?
The unofficial endpoint can rate-limit aggressive use. Because TranslatePress caches every translation in its own database, the endpoint is only called for genuinely new strings — for a typical small or medium site this is far below any rate-limit threshold. If you have a very large site or do bulk translation, consider the Pro add-on which adds AI providers as fallback.
Where are translations stored?
In TranslatePress's own database tables. This plugin does not store translations itself — it just hands them to TranslatePress.
Does this plugin send my visitors' personal data anywhere?
No. Only the page text that needs translating is sent to the configured translation endpoint, and only when TranslatePress requests it. No visitor IPs, cookies, or other personal data are transmitted by this plugin.
What happens if I uninstall the plugin?
All plugin options (haitp_settings, haitp_log) are removed from the database. Translations TranslatePress has cached in its own tables are not touched — TranslatePress manages those independently.
Is the source code available?
Yes — this plugin is GPLv2-or-later. The full source is in the plugin folder, and the development repository is linked from the plugin homepage.
Can I extend it with a custom provider?
Yes. Extend HAITP_Provider_Base, implement translate() and self_test(), and register your class via the haitp_registered_providers filter.
更新日志:
1.2.3
- Fixed a PHP notice ("Undefined variable $opt") on the settings page caused by an incorrect variable passed to the Pro section action hooks.
- The "Watch the setup & translation video" link in the Pro upgrade panel now points to the Pro version overview video.
- Removed the redundant perks line from the Pro upgrade panel for a cleaner layout.
- Added a "Watch the setup & translation video" link on the settings page so users can follow a YouTube walkthrough to install and configure the plugin.
- Updated the Pro upgrade panel to list the "Delete ALL translations" tool (clear every cached translation in one click and re-translate fresh).
- Renamed plugin to "Hybrid AI Translator for TranslatePress".
- New PHP prefix
HAITP_and text domainhybrid-ai-translator-for-translatepress. - Added
LICENSE.txt,uninstall.php, andload_plugin_textdomain()for full WordPress.org compliance. - Activation safety: blocks Free activation when the Pro add-on is already active, so the two cannot collide.
- Cleaned up provider list and settings UI.
- Initial release.