Description
Connect, translate, resume and review
Posts and Pages are the primary workflow: enable relevant languages, select important source pages, save drafts and review complete published variants. Compatible agents can use resumable plans and bounded batches for larger WPBakery pages, save private progress notes, and resume after interruption. Preserve manual corrections and use the missing/stale review queue before refreshing translations.
An administrator must separately enable integration drafting and publication in Translator settings and review the exact Site Manager tools/connection. Draft access does not grant publication. A shared relay suits a small administration team across sites; local OAuth is recommended for many users translating their own content. Manual translation needs no agent connection.
Registered public plugin-text providers and installed locale catalogs support secondary snippet workflows. Unsupported/private fields remain outside public translation capture. Advanced field adapters are demand-led; the page/post workflow remains independently useful.
Create language versions of public, unprotected Posts and Pages while keeping the original intact. Translate manually in WordPress or ask your connected AI/SI assistant to prepare drafts. Local editing needs no translation-service account, model subscription or API key from this plugin. It makes no translation-provider requests or automatic background translations.
Included features:
- Local translations of title, excerpt, content, search title and meta description, with drafts, revisions and source-freshness checks.
- Resumable private plans for longer pages: small batches, retry receipts, progress review and one complete draft. Partial work never changes a public translation.
- Native source/translation comparisons and reviewed section protection. Uncertain or moved builder sections retain whole-field protection; agents cannot unlock manual corrections.
- Safe refresh plans that reuse verified unchanged units and retain protected corrections.
- Review queues for missing/stale pages, supported plugin/user texts, unresolved protection and publication readiness.
- Private progress notes per translation and optional shared source notes from Site Manager. Notes never grant permission or enter public output.
- Published locale URLs, canonical/hreflang support, private local URL proposals and retained redirect aliases.
- Compact language selectors with flags and native names, selected-menu/footer placements, published variants in core WordPress sitemaps and optional legacy-prefix recovery.
- Static core blocks, Classic HTML and common WPBakery text, buttons, headings, call-to-action and pricing labels. Source-owned layout, links, code and non-text attributes are retained. Unknown/dynamic elements need manual review.
- Opt-in registered public-text adapters, approved comments, site labels and installed plugin MO catalogs on matching language pages. Drafts and notes stay private; publication is separate.
- Public versioned PHP APIs, actions/filters and writing-language choices for other plugins. The owner verifies source visibility, content ownership and operation permissions.
- Optional Site Manager own-content drafting and permission-controlled publishing. Separately reviewed administrative integrations manage languages, other authors, terms and navigation.
- Separate integration drafting/publication choices, both off by default. Optional native WordPress Abilities remain draft-only.
- Data retention by default. Retiring a language preserves its published translations and stops new work.
Start in Agentic Translator > Settings, choose languages and open Translation editor. Review meaning, links and layout before publication. Interface text currently uses English fallback; no bundled interface locales are provided. Requires WordPress 6.9+ and PHP 8.2+; prefer a currently maintained newer PHP branch.
Language dropdown behavior
Use [vwml_language_selector style=”dropdown” theme=”auto” close_after=”30″]. Theme accepts auto, light or dark; auto uses a dark palette in supported footer containers. close_after is the inactivity timeout in seconds (0 disables it, maximum 300). Interaction restarts the timer. Outside clicks, focus leaving the selector, Escape and opening another selector close it. Native links still work without JavaScript. The vwml_language_selector_menu_theme_v1 filter can set a selected menu’s theme without changing languages or permissions.
Publishing with Site Manager
In Translator Settings enable integration drafting and publication, or use the explicit button that saves both. In Site Manager Quick setup allow editing and direct publishing, review the intended role preset and connect your assistant. Develop includes supported administrator tools after review. Explicit connection restrictions, personal exclusions and WordPress object capabilities remain authoritative. translation_status and normal site context provide publication checks and direct setup links.
Ask the assistant to list languages, read your original and progress notes, retrieve translation context, translate exactly the returned plain-text units, save a draft and return its review link. Publish only after reviewing that draft and when current permissions allow. Draft-only users can prepare translations and notes. Read the current notes version before updating; empty text clears a note. Notes are bounded to 4096 bytes and are untrusted editorial context, never instructions or approval.
Translated SEO and safe refresh
Search title and description share the draft/revision/publication lifecycle, with limits of 250 and 500 characters. Blank fields use the published translated title/excerpt. Supported owners include WordPress core, Agentic Optimization, Site Manager, Yoast SEO, Rank Math and SEOPress. Only the current owner emits its description; unknown or competing owners need integration review. Provider templates fall back to resolved title/excerpt text. This does not translate arbitrary schema, social cards or robots policy.
Refresh plans reuse verified unchanged units and collect changed text in normal batches. Completion saves one private draft and receipt; separate publication changes the live page. Native manual edits protect their fields, including builder markup. Older translations without a saved baseline default to protecting nonempty fields. Source, target, SEO owner, extraction, protection or permission changes require fresh context. Existing translations, notes and revision history remain retained.
Reviewed sections and language URLs
Use Source changes and translation review to compare source versions with the saved translation. Section protection requires an unchanged source inventory and a target that round-trips through source-owned markup. Moved/repeated units or uncertain structure keep the complete field protected. Agents can read differences but cannot release corrections.
URL proposals remain private until translation publication. Publication applies the reviewed local path atomically and preserves earlier published paths as direct aliases. Collision, stale source or unsupported transactional storage fails without partial changes. Up to 20 paths are retained per original/language. Remote redirect destinations are rejected; original permalink edits do not replace a bound translated URL.
Links in public content and supported reusable core Navigation output follow available published Post/Page variants. External, preview/authentication, pagination and untranslated destinations remain unchanged. Bounded static navigation labels can be translated through separately authorized integrations; dynamic/fallback/split rich labels retain the original. Labels never alter the link inventory or block structure.
Resumable plans and recovery
Create a plan with a stable request key, read its next missing batch and submit each complete translated batch with its own key. Identical retries return the receipt; different payloads conflict. After reconnecting, read status instead of creating duplicate work. A plan ID is not a credential. The actor must retain source access, language eligibility and current site/connection/personal approvals.
Plans support 256 KiB source, 1024 units, 8 KiB per unit and 1 MiB assembled draft. Batches contain at most 8 units and 16 KiB source text. Plans expire after seven days; limits are 20 active/100 retained per user and 1000 per site. Atomic completion requires InnoDB for owned plan/translation tables and WordPress posts/postmeta. Closed progress can be deliberately removed without deleting originals, saved translations or notes. Administrators cannot resume another actor’s batches merely by maintaining their progress.
Public language journeys and writing controls
[vwml_language_selector style=”dropdown”] adds a keyboard-accessible language menu; the original list shortcode remains available. Native settings append it to selected menus or below the footer. Choices link only complete published translations; an available translated homepage can serve untranslated pages. Flags are decorative and accompany native language names.
Core WordPress sitemaps include published variants, respecting source indexing/canonical policy. Optional legacy zh, zh-tw and pt prefixes recover existing public originals: permanent redirects require a published variant; missing translations temporarily fall back to the original. Real pages retain precedence. A compatible local recovery adapter may resolve reviewed old slugs.
Public writing-language hooks return configured source/target choices and a default from the resolved page or site source. Owning plugins must validate and store each submitted language, retain normal permissions and register policy-aware public-text adapters. Private messages and arbitrary user metadata are excluded.
Content and cache requirements
Page translation supports public, unprotected Posts/Pages, not arbitrary custom types, ecommerce data or builder metadata. Registered public-text adapters and shared term/navigation models are separate contracts. Pretty permalinks are required; an existing locale-root page takes precedence. Network activation is unsupported; activate separately per multisite site.
Native saved previews show allowed markup without executing shortcodes/dynamic blocks or reproducing theme styling. Title/excerpt/content have a technical 1 MiB per-field limit; publication needs nonempty translated content. Review dynamic output in the actual theme. Translated responses request no caching; configure any full-page cache/CDN to bypass locale routes and purge entries when visibility/publication changes.
Optional native WordPress Abilities
Alternatively enable authenticated assistant drafting in Settings for up to 20 selected public originals, or explicitly choose own-author access to current/future public Posts/Pages. Access starts off and retains WordPress object permissions. Manual editing needs no connector.
Use a compatible Abilities client or the optional official MCP Adapter. Follow its setup/authentication documentation. The default endpoint is /wp-json/mcp/mcp-adapter-default-server; configure a private Application Password over HTTPS and revoke it when unused. This endpoint does not accept Site Manager relay tokens. Translator creates no connector credentials or OAuth server.
Discover vwml/get-translation-context and vwml/save-translation-draft, select one approved original and target, then submit the exact translated map with its expiring context. This path saves private drafts only and supports 32 KiB source, 200 units, 8 KiB per unit and 128 KiB assembled draft. Unsupported/dynamic content and protected segments need manual review; nothing is silently truncated. A signed context is not authentication. Wrong-user/site, stale, expired or revoked contexts fail; reread before retrying.
Privacy
The plugin stores configured languages, translation drafts/public snapshots, revisions with editor IDs/timestamps, private plan batches and bounded extension advice, review provenance, local route aliases and a bounded administration activity history. It makes no external service requests, records no visitor metrics, and sets no tracking cookies. Optional AI/SI assistants can request allowed source text only after administrator opt-in and WordPress authorization; their processing is covered by their own service policies. Export is administrator-only and checks edit permission on each source; credentials and visitor data are excluded.
If upgrading an earlier development build, existing provider credentials and legacy operational tables are retained but unused. They are never contacted or included in translation exports. The explicitly confirmed uninstall deletion option removes both current and legacy plugin data. Keep sensitive server configuration outside the plugin folder.
External services
The plugin makes no external service requests itself. The optional official MCP Adapter operates on your WordPress site and is documented at https://github.com/WordPress/mcp-adapter . When you request translation through a connected assistant, allowed original text is returned to that client; its configured AI provider may process the text and charge for it. The client/provider is chosen and configured by you, not selected or contacted by this plugin. Review that service’s processing, privacy policy, terms and costs before connecting; disabling access stops subsequent translator ability calls. The plugin does not collect or store their keys, register an account, send telemetry or share visitor data.
Developer integration contract
The Free plugin owns the local data and rendering contracts. VWML_API::VERSION is 1. Use its languages, inventory, context, save, review, publish and public_variant methods from an independently authenticated, capability-checked integration. Own-source access and publication are separate native settings, both off by default. Never treat the signed context as authentication: it is also bound to current WordPress user/site, source and target revisions, settings, extraction inventory and expiry. The older native abilities remain draft-only. Contexts issued before an implementation/inventory change must be reread.
Extension hooks include vwml_loaded, vwml_translation_source_fields, vwml_wpbakery_label_attributes, vwml_translation_units_prepared, vwml_integration_draft_saved, vwml_translation_published, vwml_translation_saved, vwml_language_state_changed, vwml_languages_changed, vwml_element_saved, vwml_use_public_overlay and vwml_route_url. Filters are trusted PHP extension points, not client-controlled arguments. Source fields must remain exactly title/excerpt/content strings within the safe extraction bounds. Lifecycle events expose identifiers and counts, not credentials or signed contexts. The vwml_integration_administration filter lets a trusted companion provide administration; native manage_options and applicable object capabilities remain mandatory.
Installation
Upgrading from the previous development name: deactivate the previous VideoWhisper translator, install/activate this plugin and retain the database. Both identities share translation data; do not enable uninstall deletion or uninstall the old copy to migrate. Public locale URLs, shortcode and vwml ability names are unchanged. Discovery REST routes now use /wp-json/videowhisper-agentic-multilingual-translator/v1/.
- Upload the ZIP through Plugins > Add New > Upload Plugin, or copy the plugin folder into wp-content/plugins/.
- Activate VideoWhisper Agentic Multilingual Translator on the intended site.
- Open Agentic Translator > Settings. Confirm the source language, select targets and save. Configure a pretty permalink structure if needed.
- Open a public Post or Page and use its Multilingual translations panel, or select its title and target in Agentic Translator > Translation editor.
- Enter translated fields, Save draft and review the private preview. Publish translation when ready.
- Add [vwml_language_selector] to the source content or a Shortcode widget. It displays published languages only.
- Before removing data, download a JSON export from Settings and keep a database backup for complete revision history.
FAQ
Can other plugins translate configured messages, bios, comments or reviews?
Yes. Enable a registered public provider in Multilingual Translator > Plugin texts. Adapters re-read source fields and verify ownership/operation permissions; unknown/private fields and caller-supplied ownership are excluded. Native corrections are protected by default. Site Manager Free manages own texts; separately reviewed Pro tools administer site-wide texts. Capture does not approve tools.
Selected PHP plugin domains can use installed MO catalogs, including context/plurals, without changing global/user locale. PO/POT remain editable/source formats; compile MO normally. JavaScript catalogs need their owning plugin’s support. Observed singular strings can have local reviewed overrides. Capture is bounded to 50 new/changed texts per request and 5,000 source identities per site. Changed snippet sources fall back to originals while saved translations/corrections remain available. See the public adapter contract and examples.
WordPress privacy tools handle registered users’ currently supported own overlays. Unavailable, reassigned or guest sources require administrator review; original content and other users remain.
Does it automatically translate my site?
Manual translation always works without another plugin. Optionally enable WordPress Abilities so your connected AI/SI assistant can translate selected text into drafts. This is an explicit assistant workflow, not automatic background translation. The plugin itself does not call translation providers.
Where do translations live?
In custom tables in this site’s WordPress database. Disconnecting accounts has no effect because none are required. JSON export contains the current snapshot and latest draft; a full database backup preserves every historical revision.
What happens when I change the original?
The existing translation is retained and marked stale. A form opened before a source or target change is rejected rather than overwriting newer work. Use the browser Back button to copy unsaved edits, then reload and review the current version.
Can I remove a public translation without deleting it?
Yes. Open it in the translation editor and choose Unpublish. Its content and revisions remain available, and its public link disappears. Deselecting a target language alone retains its existing published pages and stops new edits.
Can I translate protected content?
No. A source becoming private, draft, trashed or password-protected immediately becomes ineligible for translation overlays and public variant discovery. External caches must also be purged.
Which shortcodes and APIs are included?
[vwml_language_selector] and [videowhisper_language_selector] show the current page’s published versions. Use post_id=”123″ outside a singular page. The public read-only REST namespace is videowhisper-agentic-multilingual-translator/v1, with /languages and /variants/{post_id}. Operational /status is administrator-only. When an administrator opts in on a supported WordPress version, native abilities vwml/get-translation-context and vwml/save-translation-draft are available to authenticated clients. An optional MCP Adapter can expose the same abilities; this plugin adds no separate MCP endpoint. No publication ability is exposed.
Screenshots






Changelog
0.12.1
- Refresh setup guidance for resumable agent plans, protected WPBakery drafts, separate publication and missing/stale review. Translation runtime and corrections remain unchanged.
0.12.0
- Keep protected public-text parents excluded when AJAX optimization omits the membership policy owner; shared comment/review checks and signed hints fail closed.
- Support version-bound public page locale hints for registered AJAX text outputs and translating user texts into the site source language. Owning-plugin visibility, moderation, manual protection and existing agent permissions remain authoritative.
- Close language dropdowns on outside click, Escape, another selector or inactivity. Add light/dark presentation with automatic footer contrast.
- Support up to 200 text units within the existing source, per-unit and assembled-output byte limits for detailed pages.
- Site Manager Pro can adapt its complete Markdown documents through the public source-field hook, retaining originals and protected code/links.
0.11.0
- Compact menu/footer language selectors, legacy language-prefix recovery and published variant core sitemaps.
- Public writing-language hooks and additional Russian, Turkish, Swedish and Hindi language choices.
- Clear integration publication setup with one form action; retain all permission limits and protected corrections.
0.10.0
- Add a permission-checked review queue for missing/stale content, unresolved protection and publication readiness.
- Add opt-in plugin text adapters, approved comment overlays, site labels, private drafts/notes and separate publication.
- Read installed plugin MO catalogs on resolved language pages without changing global/user locale; retain source context and plural rules.
- Preserve native manual corrections, original markup/placeholders and existing permissions; integrate registered-user privacy export/erasure.
0.9.0
- Added native source differences and reviewed section protection, conservative WPBakery refresh, private localized URL proposals and published aliases.
- Accept browser form line endings during section review without changing saved corrections, version checks or the conservative fallback for markup changes.
- Added published Post/Page link resolution, reusable Navigation label contracts and bounded advisory extension/plan hooks.
- Retained ownership, publication, native review, existing data and exact connection permission boundaries.
0.8.0
- Add translated search titles and meta descriptions to private drafts, native review and supported single-owner frontend output. Original SEO, noindex and publication controls remain authoritative.
- Add conservative refresh plans that reuse verified unchanged units, protect manual/legacy fields, retain public snapshots and reject stale source, target or permission changes.
- Keep manual protection under native editorial control; expose Free hooks and explicit refresh summaries for integrations.
0.7.0
- Add actor/site/version-bound resumable translation plans, private bounded batches, exact retries, cancellation, expiry and explicit retained-progress cleanup.
- Atomically save the complete private draft and its durable receipt; retain existing public snapshots until separately authorized publication.
- Add native progress/batch review, setup links and documented integration hooks. Extend reviewed WPBakery CTA/pricing labels and accept safe inline-style serialization spacing while rejecting KSES-changing markup.
- Keep existing short-context/native Ability bounds and permissions, default data retention and English fallback.
0.6.1
- Register localized taxonomy routes after ordinary taxonomy setup and before broad language routes, then refresh cached rules on upgrade.
- Remove owned taxonomy routes when refreshing languages or deactivating the plugin while retaining customer translations.
0.6.0
- Private source and per-translation progress notes with versioned updates and authenticated retrieval.
- Language inventory includes the supported catalog; Romanian is available as an opt-in target.
- Public query integrations can select published language variants before pagination.
- Defer language-route registration and flushing until WordPress rewrite services are ready during a fresh installation or early bootstrap.
0.5.0
- Permission-controlled integration API and hooks; WPBakery text/label preservation; shared term/menu translation model.
0.4.4
- Escape translated title and document-title output; explicitly filter allowed HTML in content and excerpt callbacks.
- Limit the previous-plugin conflict notice to authorized users on the Plugins screen, remove an unused onboarding-notice hook, and require POST for legacy dismissal.
- Require WordPress 6.9+ and PHP 8.2+. Existing translations and settings are retained.
0.4.3
- Respect WordPress query filters when resolving originals for connected assistants.
0.4.2
- Assistants can identify an approved original by its same-site URL, slug/page path, exact title or ID. Ambiguous matches require clarification. Access controls and human publication remain unchanged.
0.4.1
- Rename to VideoWhisper Agentic Multilingual Translator with a matching directory identity and text domain.
- Retain translations, settings, shortcode and vwml abilities. Prevent simultaneous activation with the previous development identity.
0.4.0
- Searchable original picker, optional connected-author access, translation review list, Posts/Pages shortcuts and language statuses.
- Copyable AI/SI assistant prompts; manual review and publication remain required.
0.3.2
- Explain the verified native MCP authentication flow using Users > Profile > Application Passwords and HTTPS Basic authentication.
- Link directly to Profile and clarify private credential storage, revocation and separate client connection.
0.3.1
- Link connector setup to the WordPress.org MCP Adapter installer and identify the correct plugin/author.
- Show adapter installation/activation status and distinguish installation from client authentication.
0.3.0
- Add optional native WordPress Abilities and official MCP Adapter discovery for authenticated AI/SI assistant draft translation.
- Restrict access to explicitly selected public originals and enabled targets, with actor/site/version/expiry/consent checks.
- Extract bounded plain-text units and assemble source-owned markup; preserve code, placeholders and attributes.
- Keep manual translation and human-only publication, with connector setup, privacy guidance and review prompts.
0.2.1
- Select recent originals by title, with an older-source ID option and clear empty states.
- Add action confirmations, plain-language publication status and original-page shortcuts.
- Clarify revision recovery and preview direction, and improve small-screen editor layout.
0.2.0
- Complete manual-first publishing workflow with draft preview, unpublish, recent revision recovery and JSON export.
- Reject stale source/translation saves and preserve live content when editing drafts.
- Add reciprocal language links and supported SEO canonical integration; restrict public routes and discovery to eligible published sources.
- Remove incomplete provider tests and visitor-demand collection from runtime.
- Retain existing translation data and legacy configuration on upgrade.
0.1.2
- Preserve source password protection in overlays and public variant discovery.
0.1.1
- Add target-language defaults and onboarding navigation.
0.1.0
- Initial local development version.
