WP Virtuoso Changelog.
A transparent record of important plugin, controller, safety and platform improvements as WP Virtuoso moves toward general availability.
4.5.0-rc.14
RC14 fixes a quoted-HTML content integrity bug discovered during the live Spanish translation rollout. Generic post create/update payloads sent through the guarded Ability and batch-job layer are no longer pre-slashed before the structured WordPress command executor performs its single canonical save-boundary escaping.
Single save-boundary escaping
Quoted HTML now reaches the structured post command unchanged and is escaped exactly once immediately before WordPress saves it.
Batch HTML integrity
The RC13 path could persist literal backslashes before HTML attribute quotes in batch post updates. RC14 removes that double-slash path.
Regression coverage
Direct command writes and create-job batches now have dedicated quoted-HTML normalization tests so this class of corruption cannot silently return.
Scope kept narrow
The existing WordPress save-boundary wp_slash handling remains in the structured command executor, and the separate legacy categorized-post path is unchanged.
Validation
RC14 passed 140 release gates, 33 connection regressions, full PHP linting and both ZIP integrity checks before packaging.
Controller unchanged
Fleet Controller 0.13.0 remains current. RC14 is a WordPress-plugin-only hotfix.
4.5.0-rc.13
RC13 fixes a Polylang translation-link verification bug found during the live English-to-Spanish rollout. Separate single-language groups can no longer be mistaken for an already-linked translation group.
True translation-link checks
The no-op path now requires every member page to independently report the complete requested language map before WP Virtuoso can say the pair is already linked.
Authoritative readback
After Polylang saves a translation group, WP Virtuoso reads the relationship back from every member page and fails if the persisted mapping does not match the request.
False-success prevention
RC13 specifically fixes the live RC12 case where an English-only page and a Spanish-only page were merged in memory and incorrectly reported as an existing pair.
Conflict protection retained
Existing translation relationships remain protected by default and explicit relinking is still required before replacing an existing language member.
Validation
RC13 passed 138 release gates, 31 connection regressions, full PHP linting and ZIP integrity checks before packaging.
Controller unchanged
Fleet Controller 0.13.0 remains current. RC13 is a WordPress-plugin-only hotfix.
4.5.0-rc.12
RC12 added guarded Polylang content automation so WP Virtuoso can assign languages to real posts/pages and link translation groups using Polylang’s public APIs. The live rollout then exposed the translation-link no-op defect corrected in RC13.
4.5.0-rc.11
RC11 added safe one-approval WordPress REST batching. Its live acceptance test successfully created and verified English, Spanish, German, French, Italian and Portuguese on the remote WP Virtuoso site while keeping every nested route inside WP Virtuoso’s existing write policy.
4.5.0-rc.10
RC10 fixed canonical remote target binding so the controller resolves and seals the registered site origin before approval and replay, preventing incomplete or ambiguous multisite targets.
4.5.0-rc.9
RC9 strengthened multisite routing and write reliability with exact site targeting, fail-closed remote routing, bounded Polylang REST writes, guarded remote plugin installation, clearer approval execution states, no-op/hash receipts and refreshed fleet version metadata.
4.5.0-rc.8
RC8 improved WooCommerce batch performance and reliability by optimizing duplicate-image detection, extending legitimate remote-operation timeouts and surfacing fleet registry lookup failures instead of silently returning an empty remote fleet.
Execution is not the same as verification.
WP Virtuoso’s next build priorities include stronger post-write verification for user-visible changes, clearer separation between approved, executed and verified states, and better cache-aware front-end checks before a change is described as complete.