| 开发者 | melotools |
|---|---|
| 更新时间 | 2026年10月15日 18:45 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. The plugin is free, and Free basic needs no key and costs nothing. AI providers charge you directly for what you use. Gemini and Groq offer free tiers with limits. Set a spending limit with your provider. Note for Gemini: Google's Gemini API terms say that in the European Economic Area, the United Kingdom and Switzerland only paid services may be used, so the free tier is not available there. If you are in one of those regions, enable billing in your Google account or use another provider. Check Google's current terms: https://ai.google.dev/gemini-api/terms
Yes. It works with the free TranslatePress plugin and adds a Translate page button to its visual editor. No TranslatePress paid plan or add-on is needed.
You pay your provider for the text sent and received, so the cost depends on the length of the page and the model. Before a large run, the plugin shows how many strings and characters will be translated. Check your provider's price list, and set a spending limit in your provider account. Gemini and Groq have free tiers with limits.
TranslatePress has its own automatic translation options (such as TranslatePress AI, Google Translate and DeepL), and which ones you can use depends on your TranslatePress plan. This plugin adds a separate option: translate the current page from the visual editor with Claude, ChatGPT, Gemini or Groq using your own key, or for free with Free basic. Your existing translations are kept, so you can use both.
Any language you have added in TranslatePress. Quality depends on the provider and model you choose. The plugin warns when a result looks like the wrong script or Chinese variant.
Your provider's free tier has a limit per minute and per day, set by the provider, not by this plugin. Wait and click Translate page again: strings that were already translated are kept, so it continues where it stopped. For larger sites, enable billing with your provider or choose another model under Model (optional).
No. By default only untranslated strings are translated. Your own edits are only replaced if you explicitly choose that option for a page.
Yes. In the TranslatePress editor, click Undo last run to restore the strings as they were before your last run or clear. Strings you edited by hand after that run are left as they are. One level of undo is kept for each user.
It removes the machine translations of the strings on the current page so you can translate them again. Strings you translated or edited yourself are kept, and you can undo the clear.
The plugin warns when a result looks like the wrong script (for example Latin instead of Cyrillic) or the wrong Chinese variant. Use Undo last run, choose another model or provider, and translate again. The warning never blocks saving.
Keys belong to the user who saved them. Other administrators cannot see or use them; each person adds their own. They are encrypted in the user profile data with libsodium, using your site secret keys and the user ID, and are never sent to the browser. Only a four character hint is shown.
For stronger protection, define the key in wp-config.php instead (it then applies to every administrator on the site):
define( 'OCAT_GEMINI_KEY', '...' ); (also OCAT_ANTHROPIC_KEY, OCAT_OPENAI_KEY, OCAT_GROQ_KEY)
If you change your site secret keys (AUTH_KEY, AUTH_SALT), saved keys must be entered again.
Only when an administrator clicks Translate page or Test connection: the untranslated text strings of the page, the language names, and the optional tone and glossary text. No visitor data is sent. See External services below.
Free basic uses the translator built into Chrome and Edge on desktop. The browser may download a language pack the first time you use a language pair. Other browsers can use an AI provider instead.
Yes, on local test sites only. Add to wp-config.php:
define( 'OCAT_ALLOW_LOCAL_LLM', true );
define( 'OCAT_LOCAL_LLM_URL', 'http://127.0.0.1:11434/v1' ); (LM Studio: http://127.0.0.1:1234/v1)
A "Local AI" tile then appears. If WordPress runs in Docker, use http://host.docker.internal:11434/v1 and start Ollama with OLLAMA_HOST=0.0.0.0:11434. Never enable this on a public site.
Users with the manage_options capability (administrators). Developers can change this with the ocat_capability filter.
Post in the support forum or use the MeloTools contact page.