WakaLang

Changelog

0.6.24

• Add a public API compatibility policy (Issue #723): docs/COMPATIBILITY_POLICY.md defines hooks / REST / Abilities / GraphQL / WP-CLI as versioned public API (semver, two-minor deprecation via _deprecated_hook(), Abilities schema rules). New stable hooks: wakalang_root_language_detected, wakalang_language_url_prefix, wakalang_language_switcher_items, wakalang_translation_unlinked, wakalang_settings_schema. wakalang_hreflang_entries is now stable (wakalang_canonical_url already was, Issue #711). Track A pins the surface in tests/Fixtures/public-api-snapshot.json. WakaLang Pro cancels automation jobs on unlink; WPGraphQL urlPrefix uses the public prefix filter.
• Split three oversized Pro translation classes while keeping their public constructors, methods, and hooks (Issue #738): AiTranslationPage → controller / view / CSV exporter / job diagnostics; TranslationCoordinator → kind translators over a shared pipeline; ReviewRepository → staging / guards / decisions. Dedicated Track A tests cover ProviderRequestSupport, BlockStructureValidator, glossary and translation-memory schema helpers, and table-driven auto-translation policy gates.

0.6.23

• Add a Settings “Content schema” tab (Issue #717): for every translatable post type the detected post meta keys and the registered block types’ string attributes are listed with copy / translate-manually / ignore policy selects, stored in the non-autoload wakalang_content_schema option and resolved by ContentSchemaRegistry as a fourth sibling source — code declarations (the wakalang_content_schema filter and wpml-config.xml) still win any conflict by the most-restrictive rule, and secret/auth keys stay locked to ignore in the UI. The same declarations are exposed as the content_schema key on wakalang/get-settings / wakalang/update-settings and as wp wakalang settings get --field=content_schema / --content_schema=<json>.
• Add a Tools “Menu sync” panel (Issue #716): generate a same-hierarchy nav menu per target language from a default-language menu, with each item re-pointed at its translation-group member (the front-end fallback policy governs links with no translation), custom links prefix-swapped under the localizer’s exclusion policy, labels copied through the new wakalang_menu_sync_label filter (the Pro AI hook-in), and hand-edited labels preserved on re-runs (the sync only relabels items whose label still matches what it last wrote). Re-runs apply a diff (add / delete / re-parent / reorder, keyed by a source-item marker meta) without touching items the user created inside a generated menu; a dry-run preview reports the changes before anything is written (PRG, per-user report), generated menus are proposed for the source menu’s theme locations via the per-language MenuLocations store, and block themes get the same operation over wp_navigation posts with results registered for the front-end NavigationRefs language swap.
• Add an opt-in, non-forced language suggestion banner (Issue #710): a cache-safe front-end script offers a link to another language’s published translation of the current page when the visitor’s browser language differs, with per-language message overrides in the Tools string-translations store and a session-cookie dismissal. Off by default; the server makes no visitor-dependent decisions, so prefixed URLs stay fully page-cacheable.
• Add a per-language banner_message override to the Tools String translations panel.
• Add a Free, AI-free translation structure check (Issue #715): heading outline, link count/href set, image count, Gutenberg block-type sequence, and code-block count are compared on save and stored as _wakalang_structure_check post meta. The Translation Hub, Gutenberg sidebar, and classic meta box show a warning (never a publish block) such as “1 missing link”; Hub CSV adds a Structure column per language. WakaLang Pro’s QA Engine is not used.
• Split Plugin::boot() into per-request-type Bootstrap\{Core,Frontend,Admin,Cli,Abilities}Registrar classes (Issue #721): admin/CLI/abilities-only services are no longer generated on a plain front-end render (a front boot drops from 110 to 63 loaded WakaLang\ classes), and the shared services admin, CLI and the abilities surfaces consume are built once through a memoised Bootstrap\Container exposed by Plugin::container(). The boot sequence is behaviour-preserving; every hook still registers exactly as before.
• Add a static-state reset seam (Issue #721): classes holding request-scoped statics (HomeUrlFilter, LinkFilter, PostsCacheInvalidator, Options, SettingsSchema, and Pro’s ChunkResumeStore) expose reset_for_tests(), and WakaLang\Testing\StateReset clears them in every test’s set_up() so Track B results can no longer depend on class statics leaking across tests.

0.6.22

• Add Pro translation QA rules for HTML balance, link targets, cross-chunk terminology, Japanese register, and repeated sentences, plus a filterable site QA report, CSV export, and Site Health metrics.
• Add Translation Hub AI selection, estimate, and explicit enqueue actions, including review-only bulk SEO and slug candidates across the Hub, WP-CLI, and Abilities API.
• Add a bilingual, saved-response Pro sales demo for structure protection, glossary correction, human review, and incremental translation (Issue #766).
• Reduce front-end query overhead without a persistent object cache by priming a generation-guarded translation target map and avoiding duplicate URL reverse lookups.

0.6.21

• Backfill source_language_code and record AI-reviewed status.
• Add Gutenberg translation sidebar.
• Address code review findings for flaky test tracking.

0.6.20

• Guarantee each language’s <html lang>/dir directly from the language registry (not the installed language pack), add a dir="rtl" to right-to-left language switcher links, and add a Multilingual Doctor check for language attribute misconfiguration.

0.6.19

• Add per-language/provider AI usage breakdown with CSV export.
• Refresh plugin screenshots.

0.6.18

• Add language filter to taxonomy term list tables.
• Memoize UrlResolver::resolve_for_language() per request.
• Batch translation graph priming for REST post collections.
• Stabilize admin site-health and permissions specs.

0.6.17

• Add translation coverage dashboard widget.
• Scope dashboard widget by allow-list and fix broken empty-state link.
• Keep core sitemap alive alongside an SEO plugin.

0.6.16

• Translation Exchange (Pro) can now include excerpt, per-translation SEO title/meta description and slugs in an export via opt-in checkboxes, and taxonomy term names as a separate unit type; imports apply the new fields, hold slugs for explicit manual application, and keep title/content-only files working unchanged (Issue #466).

0.6.15

• Language switcher links now point at the clean translation URLs, matching the hreflang alternates; the preferred-language cookie is written by a small front-end script on click instead of a query-parameter redirect hop (Issue #633). The server-side ?wakalang_switch_language= flow is kept for backward compatibility.

0.6.14

• Prevent WP 7.1 handle_404 false positive on sitemap requests.
• Send 200 explicitly and tighten pre_handle_404 test coverage.
• Declare WordPress 7.1 compatibility.

0.6.10

• Add bulk approve/reject to Translation Review queue.

0.6.8

• Add translationGroupId field and own i18n catalog.
• Bump minimum Free version to 0.3.1 for TranslationGraphBuilder.
• Suppress nonce-verification false positives in Pro admin pages.
• Guard adapter package against Pro declarations.

0.6.7

• Move SEO consistency observation off front-end requests.
• Reject a redirected or empty head in the consistency scan.

0.6.6

• Speed up the Translation Hub and translation coverage report on large sites.

0.6.5

• Cap default-language assignment to a bounded batch per call.
• Batch translation group lookups in the post list table.
• Restore quality threshold baseline.

0.6.4

• Memoize merged settings and schema defaults.
• Resolve 404 fallback target via bare permalink.

0.6.2

• Add bulk language assignment to the post list.
• Add edit, enable/disable, and reorder to the Languages page.
• Add term translation search and draft creation (#442).
• Show source-change diffs and add bulk needs-update resolution.
• Add bulk translation-draft creation to the Translation Hub.
• Add confirm-before-destructive-action and notice dismissal.
• Add versioned DB migrations.
• Resolve menu items via known object id instead of URL reverse lookup.
• Fall back to a display name when no flag emoji resolves.
• Detect and recover from a missing translations table.
• Remove residual WakaLang data.
• Verify critical write results.
• Localize GFMR and CLI notices.

0.4.0

• Add site-to-site export and import of translation relationships, so language assignments and translation groups survive a WordPress (WXR) content move.

0.3.2

• Add cross-language 404 fallback resolution.