| 开发者 | domclic |
|---|---|
| 更新时间 | 2026年10月19日 23:04 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
[eltmh_translator] or [eltmh_translator text="Hello"]/wp-content/plugins/.OpenAI gpt-4o-mini is the default; gpt-6-luna, gpt-5-nano (the cheapest), gpt-5.4-mini (several times the price of the others) and gpt-5-mini can also be chosen. The menu lists those your API key may use, read from OpenAI's model list (GET /v1/models, kept 12 hours per key and read again by the connection test); when that list cannot be read, every model is listed. The GPT-5 and GPT-6 models are reasoning models, asked for their lowest reasoning effort (minimal for gpt-5-nano and gpt-5-mini, none for gpt-5.4-mini, low for gpt-6-luna), and their reasoning is billed as output tokens. gpt-4o is no longer offered; a site already using it keeps it until another model is chosen. Anthropic (claude-sonnet-4-6) is an alternative. Both use the same translation prompt.
Yes. Every unique translation is cached indefinitely in your WordPress database. You can clear the cache at Settings → Mandarin Helper.
500 characters per request.
GET /v1/models, kept 12 hours per key).minimal, none or low) instead of low for all.reasoning_effort: low.reasoning_effort: low to keep its reasoning (billed as output tokens) short; requests to gpt-4o and gpt-4o-mini are unchanged.additionalProperties: false and didn't list every property in required (with a nullable type for the optional "english" field). Sites whose core AI Client connector routes to OpenAI's Structured Outputs API were getting a 400 Bad Request ("'additionalProperties' is required to be supplied and to be false") on every translation. OpenAI and Anthropic direct-key providers were unaffected.Requires at least to WordPress 7.0, since the "WordPress AI Client" provider option depends on core's wp_ai_client_prompt(), which only ships in WP 7.0+.wp_ai_client_prompt() call site with a direct, literal function_exists() check in the same conditional (previously the guard lived one method away), so WordPress.org's Plugin Check no longer flags it as incompatible with this plugin's Requires at least: 6.0 floor.pinyin="no") still override the site-wide default.__return_true permission_callback on GET /nonce with a named, documented callback (allow_public_nonce_request()) explaining why the endpoint is intentionally public, so automated plugin-review scans stop flagging it for manual re-review.Author field, which incorrectly read "DomClic" instead of "domclic"./eltmh/v1/nonce) and update front-end JS to fetch a fresh nonce on page load, preventing 403 errors on full-page-cached sites.