| 开发者 | szymon0zawadzki |
|---|---|
| 更新时间 | 2026年6月18日 14:58 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
pa_*) such as Color, Size and custom attributespa_*)The free version allows you to translate all your content to English. All features are available.
Visit our website to purchase a Pro license. Once purchased, you'll receive a license key to enter in the plugin settings.
Yes, WPML is required. This plugin extends WPML's translation capabilities with AI-powered automatic translations.
You can get an API key from OpenAI's website. You'll need to create an account and add billing information.
Translation costs depend on the OpenAI model you choose and the amount of content. GPT-5.4-nano is the most cost-effective option. The plugin shows estimated costs before translation. Note: OpenAI API costs are separate from the Pro license.
The plugin supports GPT-5, GPT-5-mini, GPT-5-nano, GPT-5.4, GPT-5.4-mini, GPT-5.4-nano and GPT-5.5. The default model is GPT-5.4-nano, the fastest and most cost-effective option.
On activation the plugin creates a dedicated virtual user, latwaitr_ai_bot (displayed in WPML as "LATW AI Translator"), and registers it with WPML as a local translator. When you assign content to this translator in WPML's Translation Management screen, the plugin automatically detects the job, translates it with OpenAI, and returns the result through WPML's pipeline. This means anything WPML can send for translation — posts, pages, custom post types, WooCommerce products, strings and more — can be handled by the AI bot.
Yes. The plugin offers full WooCommerce integration. It translates products and their content as well as product attribute taxonomies (pa_*) such as Color, Size and any custom attributes. Because the plugin works through WPML, anything WooCommerce content that WPML can translate is supported.
Yes. The plugin integrates with WPML String Translation, so you can batch-translate interface strings, theme strings and plugin strings through OpenAI directly from the plugin.
Yes. You can define a glossary of preferred terms and their translations. The plugin applies it during translation so terminology stays consistent across your entire site.
Yes. The Translation History page lets you review every past translation, inspect what was sent and returned, and track the status of each job.
Yes, you can add a website description and custom instructions to improve translation quality and context.
Yes, the plugin has full support for Elementor and Bricks Builder. Other page builders that are compatible with WPML should also work, but have not been officially tested.
Translations are processed using WordPress Cron for reliable background processing without timeouts.
When your license expires, you can continue using the plugin version you have, but you won't receive updates. To access newer versions, you'll need to renew your license. The English only version continues to work without any license.
wpml_tm_send_jobs), so they appear in WPML's Translation Management UI, respect WPML's job statuses, and stay consistent with manual edits.LATWAITR_TS_Service - the standalone Translator, WPML integration, ACF integration and page-builder bridge classes were collapsed into one Translation Service that talks to WPML directly. Smaller surface area, fewer moving parts.rank_math_schema_* meta fields are no longer sent for translation, preventing unnecessary API calls and garbled JSONassign_terms capability is now temporarily granted when wp_insert_post / wp_update_post runs from a cron/background job, so custom taxonomy terms are applied correctlyresponse_data when a term translation completes, matching the behaviour for postswpml_page_builder_string_translated action now receives the nested [string_id => [lang => [status, value]]] format expected by Gutenberg's WPML handler, fixing layout rebuild after translationpending and dispatched to OpenAI in batches by the cron, removing the old 50-item hard limit for queueingwp_insert_post / wp_update_post, preventing WPML's publish-time sync from overwriting thempending so the dispatcher re-submits them, instead of creating a duplicate queue entrypending / Waiting... status indicator in the queue tablepending items