Lionrapid Translation

Changelog

1.4.2

• Fixed: activating Lionrapid Translation while an older copy installed from a ZIP
  (in plugins/lionrapid/) is still active no longer fails with a fatal error. The new
  copy takes over and deactivates the old one; your connection and settings carry over.
• Fixed: deleting that older copy no longer deletes your settings. Its uninstall used to
  remove the settings the two copies share, which disconnected the site.
• New: the Plugins screen and Settings → Lionrapid say when an older copy is still
  installed, and that it can be deleted.

1.4.1

• Changed: the plugin now requires PHP 8.1. On PHP 8.0 it could not be activated.
• Changed: activation no longer switches Plain permalinks to /%postname%/ by itself.
  Settings → Lionrapid says when your permalinks need changing for language addresses.
• Changed: the page-cache notice shows only on Settings → Lionrapid, not on every
  admin screen.
• Fixed: settings saved through the settings form or synced from your dashboard are
  cleaned field by field; invalid language codes are dropped.
• Fixed: the plugin reads WordPress’s own addresses (REST, admin, login) instead of
  assuming the default ones, so a custom REST prefix works.
• Fixed: the translation-editor block no longer contacts Lionrapid before the site is
  connected, and dashboard pushes are limited to one run a minute.
• Fixed: no missing-file notices or 404s for block scripts in the block editor.

1.4.0

• New: a simpler settings page. Connection, Translation and Languages each sit on one
  card, the status shows at the top (Connected, Waiting for approval, Not connected), and
  the connection code is shown large with a Copy button. Explanations moved into small ⓘ
  labels that open on hover, keyboard focus or tap. Technical details are under Advanced.
• Fixed: “Connect to Lionrapid” always starts on the first click, also before the page’s
  script has loaded.
• Fixed: a top-corner language switcher no longer covers your theme’s header menu.
• Fixed: a visitor’s browser no longer shows a stored copy of translations from another
  Lionrapid project on the same site, and a removed translation stops being shown.
• The page language (<html lang>) follows the language the visitor picks.

1.3.2

• Fixed: the first Save on the settings page, and Sync Now, could drop the languages,
  namespace and switcher settings arriving from your dashboard, while still showing a
  successful Last sync. They came back only at the next background sync.
• Fixed: with “Enable Plugin” or “Emit hreflang tags” turned off, Sync Now could turn
  them back on.
• A sync whose settings could not be saved now reports an error instead of success.
• The FAQ now says that pages in your source language are scanned too: that is how new
  strings reach Lionrapid.
• The redirect to a visitor’s language uses wp_safe_redirect(), which only follows
  addresses on your own site.

1.3.1

• Now in the WordPress plugin directory as “Lionrapid Translation”. The text domain is
  lionrapid-translation, the directory’s name for the plugin, so translations of the
  settings screen can come from translate.wordpress.org.
• The readable TypeScript sources of the bundled scripts ship with the plugin, in
  assets/src/.
• The readme describes the plugin as it is today: three switcher styles, the current
  button names, what deleting the plugin removes, the service it connects to, and
  what visitors’ browsers send to it when you use a publishable key.
• The plugin folder is now lionrapid-translation, the same as the directory
  install, so a ZIP install and a directory install are one plugin. ZIP files
  before 1.3.1 installed into lionrapid; see the FAQ before switching.
• Deleting the plugin keeps your settings while another copy of it is still
  installed.
• The translation cache rows carry the plugin’s lionrapid_ prefix. The old rows
  are removed once after updating and your translations are fetched again on the
  next page view.
• The same-origin translation endpoint moved into the plugin’s own namespace:
  /wp-json/lionrapid/v1/api/integrations/translations/{locale}/{namespace}. The
  old /wp-json/api/integrations/... address is gone. A page your host cached
  before updating may ask the old address until that cache expires; its
  server-side translation is unaffected.
• Every value read from the request is unslashed and sanitized, with web addresses
  kept intact, and each admin action checks its security token itself.

1.3.0

• The settings page now speaks plainly. Labels and messages were written for the
  developers who built the plugin, not for the people who install it — so a failure
  said things like “Invalid response format” and left you nowhere to go. Every
  message now says what happened and what to do about it.

• The server address defaults to the real one. A fresh install pointed at localhost,
  an address that only exists on a developer’s own machine, so the first connection
  test could never succeed. Sites already set up are unaffected — your saved address
  is kept.

• Every button shows its own progress and result. Test connection, Sync now, Clear
  cache and Update language URLs now behave the same way: the button tells you it is
  working, then whether it worked, and the answer stays on screen underneath instead
  of vanishing.

• When something fails you get a plain explanation and a next step, with the
  technical detail behind a “Details” link for when support needs it.

1.2.6

• Fix: visitors whose browser is set to another language now reach that language
  from your home page, even when the page is served from your host’s cache.
  Previously the redirect ran in PHP, and on a cached page PHP never runs — so a
  Finnish visitor landing on a warm home page simply saw English. The choice is
  now made in the browser, which still runs when the cache is serving.
  Your home page stays cached for everyone; only the language decision moved.

1.2.5

• Fix: a translation you removed or unapproved could keep appearing on your site
  forever. Each string was stored twice — once on its own and once inside a
  bundle — and refreshing replaced the bundle without ever clearing the individual
  copy, which is the one the plugin reads first.
• Fix: choosing your own language now sticks. Picking the site’s main language
  from the switcher could be overridden by your browser’s language on the next
  visit, sending you back to the language you had just left.
• Fix: language-prefixed URLs like /fi/about/ now resolve the same way /about/
  does, including nested pages and content from other plugins. Cache and SEO tools
  that ask WordPress “which page is this URL?” previously got no answer for a
  translated page.
• Fix: “Clear Translations” also clears the bookkeeping that tracks how fresh your
  translations are.
• Fix: deactivating the plugin now stops all three of its scheduled jobs, not one.
• New: on hosts with a page cache the plugin can clear — WP Rocket, W3TC,
  LiteSpeed, WP Super Cache — it clears it automatically when translations change.
• New: on WordPress.com, where plugins cannot clear the cache, you get a notice in
  the admin when your visitors are being served old pages, and how to clear it. It
  appears only when translations actually change, and once dismissed it stays
  dismissed until they change again.
• New: on WordPress.com your language choice is now part of the page-cache key, so
  a visitor who prefers Finnish is no longer served the page cached for an English
  visitor.

1.2.4

• Fix: “Clear Translations” now really clears them on hosts that keep a
  persistent object cache, WordPress.com among them. The rows were being
  deleted, but a cached copy was still served, so old translations came back
  and no amount of clearing helped. The same stale copies also made every
  string look like one the site had already reported, so the site quietly
  stopped sending new content to your dashboard. If your site is on such a
  host, press Clear Translations once after updating.
• Fix: the plugin’s own short-lived caches are cleared too. On a site with a
  persistent object cache those are not kept in the database at all, so the
  previous cleanup silently matched nothing.
• Change: a resync from the dashboard now refreshes translations as well as
  settings, so an edit reaches your site without waiting for the next
  scheduled check.

1.2.3

• Fix: translation changes now appear on the FIRST page load. The refresh ran
  after the page had already been sent, so a page always showed the previous
  version and a reload was needed to see an edit.
• Fix: saving a new API key no longer silently reverts to the old one. The
  settings page reported success while the previous key was written back.
• Fix: the server URL you configure is the one the plugin calls. A legacy
  setting could override it invisibly, so requests went to the old host and
  failed with an error blaming the API key.
• Fix: the dashboard’s minimum-text-length setting now reaches the site. It was
  declared and honoured everywhere except the one place that reads it from the
  server, so sites stayed on the built-in default.

1.2.2

• Fix: “Clear Translations” now actually clears them. It was deleting from a
  cache layer the plugin never wrote to, and reported success because the delete
  matched zero rows rather than failing.
• Fix: the source-language home page is reachable again. A visitor arriving at
  your site with no referer — a typed address, a bookmark, a search result — was
  redirected to their guessed language every time, with no way back to /. An
  inferred language now redirects once; an explicit choice from the switcher
  still always applies.

1.2.1

• Fix: og: and twitter: social preview text is now translated. A shared link
  showed the source language even on a translated page, because the preview
  meta tags were never extracted for translation.
• Housekeeping: removed translationMode, a setting nothing ever read.

1.2.0

• Feature: regional locale routing (for example /pt-br/), with BCP-47 hreflang
  and Accept-Language quality-value parsing.
• Feature: SEO plugin coexistence — Yoast and similar plugins are detected, and
  canonical/hreflang output defers to them instead of emitting a second,
  conflicting set.
• Feature: localized sitemap alternates for Yoast.
• Feature: honours the noindex-locales setting, so a locale still under review
  is not indexed before it is ready.
• Change: the plugin authenticates with a publishable (pk_) key, and prefers
  the API host the server advertises over a hardcoded one.

1.1.2

• Fix: background sync no longer retries in a loop when the API key is missing
  or the server answers 4xx.
• Fix: no If-None-Match header while the translations cache is empty — the
  request could return 304 with nothing to render from.
• Fix: exact attribute-name matching when detecting no-translate markers, so a
  name that merely starts the same is no longer treated as a match.
• Fix: the fallback class loader mirrors src/ again, so a fresh install cannot
  fatal on a class the loader never required.

1.1.1

• Security: hex-escape the inline config script so a config value cannot break
  out of the <script> tag (including the <!--<script> mXSS vector).
• Fix: editor-pushed formatted translations now store under the real
  translation key instead of a numeric style index.
• Build: the release now fails if the readme Stable tag and plugin header
  Version drift apart, so wp.org always ships the built version.

1.1.0

• Feature: attribute translation — alt, title, placeholder, meta and input
  values.
• Feature: href and canonical rewriting on localized paths.
• Feature: auth-page contract — configured paths never sync keys (GDPR).
• Fix: the same-site referer guard never fired, because a bare host was
  compared against one carrying a port.
• Fix: /{lang}/ home now resolves in the request filter, rewrite rules flush on
  a language change, and the locale redirect is skipped during editor sessions.
• Fix: decode HTML entities in the markup parser, so PHP and JavaScript derive
  the same translation key for the same text.

1.0.1

• Fix: translated Pages (not just Posts) now resolve at /{lang}/ URLs.
• Fix: editor URLs like /es/?__lr_editor= no longer 404 (query string was
  being captured as the post slug).
• Add: pretty permalinks are enabled automatically on activation when the
  site is on the default plain structure (a custom structure is left
  untouched), so /{lang}/ routing works out of the box.
• Fix: config-sync cron is scheduled on init, silencing a WP 6.7
  “textdomain loaded too early” notice.

1.0.0

Initial public release.

• Server-side block-level translation via output buffering.
• Dashboard-managed config sync: languages, namespace, switcher, exclude paths, output-buffering toggle pulled from the LionRapid server.
• Real-time config push via POST /wp-json/lionrapid/v1/resync from the dashboard.
• 5-minute wp_cron fallback for config sync.
• Gutenberg blocks: translation, language switcher, translation editor.
• Language switcher auto-inject with four styles.
• URL prefix routing for non-source languages.
• SEO hreflang + translated meta descriptions.
• Background sync of newly discovered keys via wp_cron.