Gloty – AI Translation & Multilingual

By wpshelf

0+ active installationsVersion 1.82.0

AI translation for WordPress in 38 languages. Every translation is stored in your own database and served locally — no API call at render time.

Description

Gloty translates your WordPress site with AI machine translation, then stores every translation in your own database and serves it from there. Rendering a translated page never calls a remote service — page delivery stays local and deterministic even if the translation service is slow or unreachable.

The plugin is free. New customers can try the hosted translation service with a one-time allowance of 50,000 characters for one site, with no card required. Start the free Gloty trial or view translation plans and the one-time pack. Saved translations keep serving locally after the allowance is used; generating more translations needs available hosted allowance.

Serving those pages is built to be cheap. Gloty compiles your translations into a PHP cache file that your server’s OPcache holds in shared memory, so once it is warm a translated page view costs no database queries for translation at all, and the translations take almost no memory in the request. That is aimed squarely at ordinary shared hosting with no object cache, which is where a translation plugin normally slows a site down most. Where the technique is unavailable, Gloty serves from the database instead and the page is still correct.

The picker offers 38 languages, each with the right hreflang code emitted for it. That list is deliberately shorter than it could be: it is the set both AI engines’ vendors say their models support, rather than every language code in existence. A translation you cannot judge the quality of is worth less than one you can, so Gloty offers the ones where the engines are known to be strong, and every translation it produces is editable by hand.

Producing a translation does require an external service, because machine translation is not something WordPress can do locally. Gloty sends the text that needs translating to the hosted Gloty translator service, which translates it and returns the result to your site in the background. The results land in your WordPress database, are editable by hand, and keep serving with no further external calls.

Key Features:

  • 38 languages — the set both AI engines’ vendors list as supported, each with the right hreflang code
  • Your database, your translations — stored locally in WordPress, never fetched remotely at render time
  • Fast on slow hosting — translations compile into a cache your server holds in memory, so serving a translated page costs no database queries once warm; it falls back to the database safely if your host cannot do that
  • Automatic page translation — captures page output, extracts translatable text, queues it for translation
  • Entity-aware — posts, pages, taxonomies, and template strings are tracked as distinct sources with stale detection
  • Edit any translation — review and correct translations from Gloty → Translations
  • Prepare a language before publishing it — translate in the background, check it over, then show it to visitors
  • Let someone correct translations without making them an administrator — optionally limited to one language
  • A different image per language — for screenshots, diagrams and packaging that carry words
  • The language switcher in your menu — as ordinary menu items your theme styles, plus a block
  • A sitemap of your translated pages — so search engines can actually find them
  • Translate content that loads after the page — load-more, AJAX filters and search panels
  • Manual edits are protected — machine sync never silently overwrites a human correction
  • Glossary — terms that must never be translated, or that must always render a specific way per language, promotable in one click from any translation you are looking at
  • SEO-friendly — hreflang tags, translated meta, clean /fr/page/ URLs, and optional translated page addresses (/de/ueber-uns/)
  • Language switcher — floating widget, footer list, shortcode, or sidebar widget
  • Optional browser-language redirect — off by default, crawler-safe, remembered per visitor
  • WooCommerce compatible — products, cart, checkout, store AJAX fragments, and order emails sent in the language the customer shopped in
  • Gettext integration — translates WordPress, theme, and plugin UI strings
  • AI translation engine — OpenAI or Google Gemini, selected for you by the service on every plan
  • Background processing — queued dispatch with webhook delivery and a polling fallback
  • Export and import — hand a language to a translator as XLIFF or CSV, load their corrections back, or simply take a copy of your translations
  • WP-CLI — wp gloty export, wp gloty import, wp gloty languages
  • Developer extensible — filters and a REST API

How it works:

  1. Install Gloty and connect your site to the Gloty translator service
  2. Add your target languages
  3. Gloty discovers translatable content from your posts, taxonomies, and template strings
  4. Translation runs in the background and the results are written to your database
  5. Visitors get translated pages under language-prefixed URLs (/fr/, /de/, …) and can switch languages from the switcher

Translation requires an external machine-translation service. See External services below for exactly what is sent and to whom.

Documentation: https://wp-shelf.com/gloty/docs/

External services

Gloty cannot produce translations without an external machine-translation service, because machine translation is not something WordPress can do locally. This section describes every external request the plugin makes, what it sends, and when.

Nothing is sent anywhere until you have connected your site and translation has been triggered (by a scan, a Translate action, or scheduled background dispatch). Serving an already-translated page makes no external request at all.

1. The Gloty translator service

All translation work is performed by the hosted Gloty translator service. The plugin does not contact machine-translation providers directly; it sends work to the Gloty service, which selects and calls the translation engine on your behalf and delivers the results back to your site.

  • Service host: https://gloty-api.wp-shelf.com (overridable by defining the GLOTY_SERVICE_URL constant, for example to point at a self-hosted instance of the service).
  • What is sent: the source text to be translated (page, post, taxonomy, and template strings from your site), the source and target language codes, your site URL, and a per-site API token and license key used to identify and authenticate your site.
  • What is not sent: Gloty does not read text off your cart, checkout, order or account pages, because those are written about one customer rather than for every visitor, and it skips any string carrying an email address that is not your own. If a page of yours shows a customer’s details and you translate it, tell us — that is a gap, not a setting.
  • When: on connection verification, while dispatching queued translation batches, when polling for results, and when the service delivers results back to your site over a signed webhook.
  • Who: the Gloty translator service, operated by WP Shelf.
  • Terms of service: https://wp-shelf.com/terms
  • Privacy policy: https://wp-shelf.com/privacy

The Gloty service in turn passes your text to the AI translation engine it selects for the batch — OpenAI or Google Gemini. Their terms apply to that processing:

  • OpenAI — https://openai.com/policies/terms-of-use / https://openai.com/policies/privacy-policy
  • Google Gemini — https://ai.google.dev/terms / https://policies.google.com/privacy

2. WordPress.org translation packs

When you enable a language, Gloty asks WordPress.org to install the official WordPress and plugin language packs for that locale, using WordPress core’s own updater. This is the same request WordPress itself makes and sends no site content.

Gloty does not send analytics, telemetry, or usage tracking anywhere. The optional browser page-view counter described in the changelog posts to your own site’s REST API and nowhere else: it is not an external request, it carries only the language of the page, and no third party is involved.

Filters

gloty_compiled_map_enabled

Whether Gloty may compile your translations into a PHP cache file for OPcache to hold in memory. The value passed in is Gloty’s own verdict on whether the server can benefit — return false to switch the feature off entirely, in which case translations are served from the object cache, a transient, or the database, exactly as in earlier versions.

add_filter( 'gloty_compiled_map_enabled', '__return_false' );

Returning true forces it on where Gloty could not confirm OPcache is active — useful when opcache.restrict_api hides the OPcache status from plugin code. Do not force it on where OPcache is genuinely off: every request would then compile the cache file from source, which is slower than the database read it replaces.

Defining GLOTY_DISABLE_COMPILED_MAP as true in wp-config.php disables it before any filter can run, and Gloty honours WordPress’s own DISALLOW_FILE_MODS constant without any configuration.

gloty_compiled_map_max_bytes

The largest cache file Gloty will write, in bytes. Default 8 MB. A translation set that would exceed it keeps using the database.

Source code

The admin interface is compiled from JavaScript sources before release. The uncompiled, human-readable sources for everything in build/ ship inside the plugin under src/, together with the build configuration in webpack.config.js and package.json. The bundles are produced by @wordpress/scripts (webpack) via the build script in package.json; no minified or obfuscated code is included without its source.

Security

Found a security issue? Please email hello@wp-shelf.com rather than opening a
public support thread — a forum post is world-readable the moment you send it,
on a plugin installed on other people’s sites. You will get an acknowledgement
within 72 hours, and credit in the changelog unless you would rather not have it.

How do I review translations captured for one post or term?

Open Translations, find a row with a Post or Term context, and choose Review this post or Review this term in its row actions. The workspace groups the cached strings captured for that exact item, including body segments. Your language, status, staleness and wording filters still apply. Clear content item returns to the wider list. Shared theme and interface strings may also appear on the item’s pages; they keep their own capture context and are not included. This does not scan a page, request translation work, or change file exports.

How can I keep an unsaved manual translation if saving is unavailable?

In the translation editor, choose Download unsaved translation to request a private text file with your exact current wording and a source clue. The same control is available for a retained inline draft when its list cannot be read. It does not save, approve or apply a translation. Keep the file private; reopen the correct translation and manually paste the wording when ready. A download request does not confirm that your browser saved the file, so check Downloads before discarding your edit. In the table editor, leaving the field still attempts its normal save.

Installation

  1. Upload the gloty folder to /wp-content/plugins/
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Open WP Shelf → Gloty → Setup. New customers can start the free hosted trial: 50,000 characters once for one site, with no card required. Already have an account or license? Choose I already have an account or license, copy your Gloty key from the WP Shelf dashboard, and connect with that account’s email address.
  4. Add your target languages in Setup or under WP Shelf → Gloty → Languages
  5. Follow Setup to scan content and begin background translation. Review the translations before making a language public.

The setup guide covers each step in more detail: https://wp-shelf.com/gloty/docs/getting-started.html

FAQ

Do I need an account?

Yes, to generate translations with the hosted Gloty service. Open WP Shelf → Gloty → Setup to connect. New customers can start a one-time free trial of 50,000 characters for one site, with no card required. If you already have an account or license, choose I already have an account or license and use your Gloty key from the WP Shelf dashboard with that account’s email address. Without a connection, Gloty can still store, manage, and serve translations you already have, but it cannot generate new ones.

How much does it cost?

The plugin itself is free and GPL-licensed. The hosted service gives new customers 50,000 characters once for one site, with no card required. Paid monthly plans and a one-time translation pack are available for more work; see Gloty translation plans. Every plan translates on the same AI engines. Your existing translations continue to serve regardless of plan or status, because they live in your own database.

Are translations stored on an external server?

Your translations are stored in your own WordPress database, and translated pages are served from there with no external call. However, producing a translation in the first place does send the source text to an external machine-translation service — see External services above for exactly what is sent and to whom.

My language isn’t in the list. Can you add it?

Ask and we will look at it. The list is the set of languages the AI engines’ own vendors say their models support, which is why it is shorter than the language list you may have seen on other plugins. Adding one means checking that the current engines actually handle it rather than just producing confident-looking output, so it is a real answer rather than an automatic yes.

Does it work with page builders?

Yes. Gloty captures translatable text from rendered output as well as from WordPress entities, so it works with Elementor, Beaver Builder, Divi, and other page builders.

Can I edit translations manually?

Yes. Go to Gloty → Translations, find the string, and edit it. Manual edits are marked as such and are never overwritten by later machine sync.

Does it support WooCommerce?

Yes. Gloty translates product titles, descriptions, attributes, and the cart and checkout pages, including WooCommerce’s AJAX cart fragments.

For orders placed through classic or block checkout, Gloty records the customer’s active language on the order and uses it when WooCommerce sends order emails, including later status updates. Email text uses installed WooCommerce language packs and translations already saved on your site; prepare the target language before relying on it for customer emails. Orders without a recorded Gloty language keep the site’s normal email language. Check custom email templates and extensions on your store; email delivery does not wait for fresh AI translations.

What happens to my translations if I deactivate Gloty?

Deactivating stops translated URLs from being served but leaves all data in place. Deleting the plugin runs an uninstall routine that removes Gloty’s tables and options, so export anything you want to keep first.

Will this slow my site down?

Serving a translated page is designed to cost nothing extra. Gloty compiles your translations and your glossary into a PHP cache file kept in your server’s OPcache, so once it is warm a page view runs no database queries to translate, makes no remote call, and holds the translations in shared memory rather than copying them into every request.

The cache is written in the background, never during a visitor’s page view, and rebuilds within about a minute of a translation changing. Until it exists — a fresh install, or just after an edit — pages are served from the database exactly as earlier versions did: correct, just not yet as fast.

If your host has no OPcache, if the uploads directory is not writable, or if a cache file is ever damaged, Gloty notices and serves from the database instead, and reports it under Dashboard → Issues. Nothing about this can make a page render incorrectly, only more slowly.

Where does Gloty write files?

Only one place: a gloty-cache folder inside your uploads directory, holding the compiled translation cache described above (with wp-content/cache/gloty as a fallback if uploads is not writable). The folder carries an index.php and .htaccess so the files are not browsable, and each file refuses to output anything if requested directly. Deactivating the plugin deletes them; uninstalling removes the folder too, and only ever removes files Gloty can prove it wrote.

Screenshots

Changelog

1.82.0

  • Correct sidebar navigation announcements and connection-status text contrast.
  • Machine-readable responses, including the block editor’s template lookup, bypass full-page translation capture and link rewriting based on their final response type.
  • Scope editor translation reviews to the open page. Retain drafts across language/source changes and require the original review context before saving.
  • Use the site’s public React factory for JSX while retaining the existing WordPress minimum.
  • Focus page-readiness comparisons on wording, visibility or delivery attention, and download the full private checklist.

1.81.2

  • Region flag emojis work on older WordPress hosts without the mbstring extension.

1.81.1

  • Keep the freshest first-language receipt from the final comparison check and refuse mixed page/site setup observed during the comparison, including password protection or translation-cache changes.

1.81.0

  • Compare one page across up to twenty active target languages with current wording, source-change, visibility and bounded delivery facts, plus exact-language review. Failed or mixed-source reads withhold the full comparison.

1.80.1

  • Keep primary button labels readable on hover with the corrected shared stylesheet.

1.80.0

  • Added an administrator launch checklist for one published page or product and target language, with current source/capture checks, protected manual wording, bounded delivery history and draft-language visibility.
  • Checks are local and read-only. Resume a post/language check or open that exact content item for review without starting translation work.

1.79.2

  • Tools → Site Health → Info now has a WP Shelf section showing which installed shelf plugin supplies the shared admin code and stylesheet, each copy’s revision and each plugin’s version, for support.

1.79.1

  • Ask before Gloty menu changes discard unsaved translation wording; cancellation keeps the editor and matching address.
  • Protect unsaved wording when a shelf screen requests navigation.

1.79.0

  • Download exact unsaved translation wording as a private text recovery copy from the modal editor or retained inline draft.
  • Warn before leaving a dirty inline translation, including when its list becomes unavailable.
  • Retry a failed local copy without saving or releasing the existing discard protection, including while an explicit save is pending.

1.78.1

  • Guard line-feed and full-width formula prefixes in translation CSV files while retaining round-trip wording.
  • Recover stalled saved-glossary reads after 15 seconds through an explicit retry.
  • Explain private glossary export scope and recover failed local downloads without changing saved rules.

1.78.0

  • Source lookup contains noisy or throwing WordPress reads and returns a bounded unavailable response, preserving a clean retryable JSON result.
  • Captured-content lookup offers retry after a 15-second wait, keeps the source reference, and cancels retired requests when the reference or edit context changes.
  • Source URL lookup respects the current WordPress home directory, refusing neighboring same-origin sites and ambiguous escaped paths before resolving a post ID.
  • Find captured page or product translations from a source-language URL or WordPress post ID, without scanning content or spending characters.
  • Keep active translation edits safe and ignore outdated lookup replies.
  • Keep the phone header readable by placing connection status below the product name.

1.77.0

  • Translate AIOSEO titles, descriptions, social tags and page schema from local translations, with language metadata matching the page.
  • Capture image descriptions approved and applied by SnippetGrove for translation, without collecting unrelated media captions or changing the original image text.

1.76.0

  • Keep derived protected rules disabled across name syncs: use Disable instead of Delete, with the same server policy in free and Pro screens. Manual deletion remains version guarded.
  • Glossary authoring, re-enabling, bulk rules and promotion move to the separately licensed Gloty Pro add-on.
  • Translation and applying existing glossary terms remain free. Read/export and guarded disable/delete retain reviewed row versions; saved work stays available.
  • Keep local edit wording through a refused Pro save and direct installed owners to their existing license connection.

1.75.0

  • Recognize a selected post or term by its current WordPress name and open its source editor while reviewing captured translations. Details are shown only when you can edit that source; the editor link waits while a translation edit is open, and captured wording and review permissions stay unchanged.
  • New public categories, tags and custom-taxonomy terms enter local translation review when created, without needing a second edit or content scan. Private-taxonomy creation is left out.

1.74.1

  • Keep an unsaved inline translation selectable for copying while its list cannot be loaded or its row leaves the current results. Retry keeps the exact wording; explicitly discard an off-view draft to release its local editor.

1.74.0

  • Treat incomplete or malformed translation-list responses as unavailable and offer Retry, preserving filters and open drafts. Valid empty lists still show as empty; unsafe row identities and nested text are withheld before row actions become available.

1.73.0

  • Added: choose Content order while reviewing one captured post or term: title and summary first, then body parts in numeric order across server pages. Recently updated remains the default. Column sorting pauses during Content order; editing, language permissions and guarded saves retain their existing behavior.

1.72.0

  • Review cached translations captured for one post or taxonomy term directly from a row’s actions, including segmented body text.
  • Keep the selected content item visible across pagination, filtering and read retries; clear it explicitly to return to the wider list.

1.71.0

  • Preserve drafts after an unconfirmed glossary save and offer a stored-term reload before reviewing a new save; a lost acknowledgement is not proof the write failed.
  • Glossary editors refuse to overwrite a term changed or removed since it was opened. A refusal keeps the draft and offers a fresh list read before reopening; older clients retain their existing update contract.

1.70.0

  • Retry unavailable glossary lists without treating failed reads as empty. Keep search and open drafts while stale rows and mutation controls wait for a fresh list.
  • Keep saved glossary wording for inactive languages when editing a Translate as rule. Review and copy that wording without activating the language; active-language edits work as before.
  • Explain that saving Never translate removes all per-language wording, including inactive languages.
  • Keep glossary drafts open when active languages cannot be read or a newly inactive language has changed wording; refuse the whole save instead of silently dropping the edit.
  • Keep validation and refused-save explanations visible inside the glossary dialog, with sentence-case labels and explicit retry.

1.69.0

  • Filter translations by content origin while retaining language and review protections.
  • Recover unavailable translation lists with Retry while preserving drafts and preventing actions on stale rows.
  • Restore consistent sorting, filter and pagination styles in interactive tables.

1.68.0

  • Compare current stored wording after a refused translation save without discarding your editable draft.
  • Explicitly adopt the compared version before a separate save; later competing edits remain protected.

1.67.0

  • Stop repeated manual translation requests after the current request; leaving Sync also stops its next dispatch. Submitted and scheduled jobs continue.
  • Skip through a captured translation review without saving unchanged wording as a manual edit; protect dirty drafts and pending saves.
  • Keep translation review controls within narrow screens on older WordPress versions.
  • Show each Gloty screen’s name in the browser tab when opening a hidden admin page directly.

1.66.1

  • Fix: keep settings and role selections stable during saves; failed role reads offer a retry and cannot submit an empty access list.
  • Fix: keep the glossary editor and its wording in place until a pending save finishes.

1.66.0

  • Finished sync jobs are now cleaned up daily: completed jobs after 30 days, failed jobs after 90, in small batches. Translations are kept and nothing is translated or charged again. Adjust with the gloty_completed_sync_job_retention_days and gloty_failed_sync_job_retention_days filters, or define GLOTY_DISABLE_SYNC_JOB_PRUNE to keep every job.
  • Translated pages render faster: repeated interface strings and taxonomy terms are resolved once per page instead of on every call.
  • Removed two duplicate indexes from the translations table on sites upgraded from older versions, making translation writes lighter.

1.64.7

  • Refuse stale manual reviews in current editors without losing the draft; explicitly reload current wording before reviewing again. Legacy clients and file imports retain their previous behavior.
  • Review the rest of a loaded translations page with Save and next, retaining the current draft when a save cannot be confirmed.
  • Protect unsaved manual wording with explicit discard and block duplicate saves or dismissal while a write is pending.

1.64.6

  • Keep translation admin and editor screens available on supported older WordPress versions.
  • Load the glossary batch dialog correctly when Gloty is the only WP Shelf plugin installed, and retain usable keyboard focus after adding terms.
  • Preview and add up to 100 never-translate terms in one reviewed batch, keeping existing rules and confirmed saves through stop and retry.
  • Search glossary rules across source terms, notes and all stored translations, including inactive languages.

1.64.5

  • Clarified the free hosted trial, existing-license setup steps and links to translation plans.
  • Corrected the WooCommerce order-email FAQ to describe the shipped checkout-language support and its requirements.

1.64.4

  • Cancellation is only reported after it is saved, and late job responses no longer reopen cancelled work.
  • Retry incomplete cancellation cleanup from the queue without restarting remote translation.
  • Keep manual edits and completed translations while conservatively deferring cleanup shared with another active job.

1.64.3

  • Show translators only the actions they can perform, keep language filters aligned with their active assignments, and make the editor sidebar available to authorized translators.
  • Report failed manual saves without recording a successful edit, preserve unsaved text for retry, and keep administrator-only health checks off translator screens.

1.64.2

  • Fixed: a reactivated target language can receive current translations after missing a source edit while disabled. Delayed results still cannot replace newer source text or manual edits.
  • Fixed webhook and polling delivery retries after database write failures, including job-completion failures and interrupted result pages.
  • Protected newer source content and concurrent manual corrections from delayed machine translations; stale machine output is translated again instead of reused.
  • Fixed incomplete-source repair to check each context’s active-language coverage, and stopped repeated polling cursors from holding a background request open.
  • Restored the language-switcher block’s editor icons with the supported WordPress language icon.
  • Fixed translation sync completion after target languages change: translations in disabled languages no longer hide missing active-language translations.

1.64.1

  • Fixed: on a site with a static front page and a separate posts page (Settings → Reading), the language switcher on the posts page sent every language to the front page — /de/ instead of /de/blog/, and the same on /blog/page/2/. It now links to the posts page, and to the same page number, in each language.
  • Fixed: switching language on a search results page led to a “page not found”. The translated address of a search, such as /de/search/shoes/, now shows the results in that language, the same as /de/?s=shoes always did.
  • Fixed: with “Translate page addresses” on, the language switcher and the language menu items on a page with a translated address, such as /de/ueber-uns/, linked to /ueber-uns/ for English — a page that does not exist — and kept the German slug for every other language. Each language now links to that page’s own address in that language.
  • Faster: the list of your languages is read from the database once per page instead of once for every part of Gloty that needs it, about fifteen times on every visitor page. Adding, removing or editing a language still takes effect immediately.

1.64.0

  • New: if your license key stops being accepted — for example because we replaced it at your request — Gloty says so in Needs attention and on the license card, with a field for the replacement key that reconnects this site without using another site slot. Before, it reported that the licensing service could not be reached and offered only Retry. Translations keep being served while you replace the key.
  • Changed: on a site running several WP Shelf plugins, the newest version of the shared admin styles is used, whichever plugin was installed or updated last. Before, updating an older WP Shelf plugin could make every WP Shelf screen fall back to its older styles.

1.63.3

  • Fixed: a translation that came back with part of Gloty’s own request stuck to its end — text such as ','kind':'heading or ','kind':'seo_title','doc':'post:1807 after the translated words — is no longer stored or shown. It is a stray piece of the translation service’s instructions, not part of the translation, and it appeared in headings, menu labels, SEO titles and image captions. Gloty now refuses it and asks for that piece of text again, and no longer copies an affected entry onto other pages with the same text. Ordinary text that merely contains the word “kind” or apostrophes is unaffected. A refusal is written to the audit log with the value that was rejected. This fix first shipped as 1.61.1 to a single site and had not reached the 1.62 and 1.63 releases.

1.63.2

  • No visible change: on a site with no licence key, the plugin no longer reads the licence server’s address on every admin screen that checks licence state. It was one database query per screen whose result could never be used. The shared WP Shelf code now checks for a key first.

1.63.1

  • Fixed: on a phone, Gloty’s navigation took up most of the screen above every page. It was a full-width list, one row per screen — about 280 pixels of a 667-pixel phone, every visit. The links now flow as a compact wrapped row with the group headings dropped, which is the layout the rest of the WP Shelf screens have used since they stopped hiding their navigation on small screens. Nothing is unreachable, and nothing changes on a desktop.
  • Fixed: Gloty’s screens faded in even when your system is set to reduce motion. Gloty switches screens without reloading the page, so that fade was the one piece of movement a motion-sensitive user met on every click. “Reduce motion” now turns it off, as it already did for the progress bar and the toasts.

1.63.0

  • New: the “Add language” box now warns you when the language you picked covers more than one regional variant. Chinese and Portuguese are one tag each here, and nothing in Gloty chooses between Simplified and Traditional Chinese, or between Brazilian and European Portuguese — the translation engine decides. The warning appears the moment you pick the language, before anything is translated or charged, and says to read the first pages before making that language public. Nothing was removed: every language that was offered before is still offered.
  • Fixed: that same box claimed regional variants like en-GB and pt-BR “are supported”. They have not been offered since 1.31.0, when the language list was cut back to the languages both translation engines are documented to handle. It now says so.

1.62.1

  • Fixed: after paying for an upgrade, the Billing screen said your plan had been refreshed before it had. Stripe sends you back to WordPress the moment a payment succeeds and confirms it to us separately a moment later, so the screen was announcing a new plan over the old one — and then remembering the old one for up to 15 minutes. It now says the payment was received, keeps checking for about a minute, and confirms the plan only once your licence actually reports it. Closing checkout without paying is acknowledged too, instead of leaving “checkout=cancel” in the address bar with nothing said.
  • Fixed: if your browser blocked the checkout tab from opening, the Upgrade button appeared to do nothing at all. It now tells you to allow pop-ups for the site and try again.
  • Fixed: the “quota exceeded” notice discarded every reason an upgrade could not start — an unconfigured billing server, a licence that already has a subscription, a blocked tab — so the Upgrade link on it was silently dead. It now says what happened, which matters most at exactly the point translation has stopped.

1.62.0

  • New: an optional setting counts page views from the browser, for sites behind a page cache. Cached pages are served without starting PHP, so Gloty never saw those views and the per-language split was both low and unevenly low — the languages your cache served best looked the least popular. Turn on Settings → Analytics → “Count views from the browser” and a small script reports the view instead, sending only which language the page was in: no IP address, no page address, no referrer, no account and no identifier of any kind, and nothing leaves your site. Server-side counting switches off at the same time, so each view is still counted exactly once. Off unless you turn it on. The trade-offs: a visitor with JavaScript disabled is not counted, and if a plugin combines your site’s JavaScript, exclude the “gloty-page-view-beacon” handle from it.

1.61.0

  • New: Analytics now draws the trend as well as the totals. A chart above the table plots views per day across the range you picked, with the busiest day labelled, and each language in the table gains a small trend line of its own. Hover the chart — or focus it and use the arrow keys — to read a single day, including its split by language. Each row’s trend is scaled to its own busiest day, so the shapes compare but the heights do not; magnitude stays in the Views column. On a site with only one day on record the chart says so rather than drawing a line through a single point, and a range with nothing in it says which of the two reasons it is empty.

1.60.0

  • New: the “identical to their source” warning now links to the rows it is counting. Translations → Flagged → “Identical to its source” lists exactly that set, read from the same scan the number was counted with, so you can see what is behind it before deleting anything — deleting a row asks for that text to be translated again and spends your allowance. Product names, codes and text already written in the target language are left out of the list exactly as they are left out of the count.

1.59.0

  • Changed: wp gloty export now always writes to standard output, and the --file option is gone. Redirect to save it: wp gloty export de > de.xliff, or wp gloty export de --format=csv > de.csv. A plugin should not write files to a path of its own choosing, and the shell already does this better. wp gloty import de.xliff is unchanged.

1.58.4

  • Also stop reporting a product name followed by a single ordinary word — “Montale Intense Cafe decant” — as identical to its source. One word beside a name is a label, and it is usually the same word in every language.

1.58.3

  • Stop reporting a translation as identical to its source when it is a product name, a code, or text already written in that language. Those are correctly the same in both languages, and removing them to ask again would have spent your allowance for the same words back.
  • Remove exactly the rows that were reported, and no others.

1.58.2

  • Stop reading text off cart, checkout, order and account pages, and stop capturing any string that carries an email address other than your own. Those pages are written about one customer, and their text was being sent to the translation service like any other. Translation of those pages is unaffected.

1.58.1

  • Refuse a result the translation service sends in a shape that is not text at all, instead of storing the word “Array” as the translation.

1.58.0

  • Fixed: a translation that came back as the words [object Object] — a stray value from a translation provider, not a translation at all — is no longer stored or shown. Gloty now refuses it and asks for that piece of text again. If you have seen those words on your site, the affected entries will fill in on the next sync.
  • Fixed: when a provider answered with a plain list that was missing an item, every later translation could be saved against the wrong piece of text, so paragraphs appeared under the wrong heading. Gloty now only trusts a plain list when it answers every item exactly once, and re-asks otherwise.
  • A refusal is written to the audit log with the value that was rejected, so you can see it happened rather than wondering why a phrase stayed in English.

1.57.0

  • Fixed: text a theme writes straight into a plain container — a <div>, <section>, <header> and so on — was invisible to Gloty. It was never picked up, so it was never translated, and it stayed in the original language on every translated page. A container counts when it holds nothing but text and inline formatting, so page layout is still ignored.
  • Fixed: image alt text now shows a translation when Gloty already has one for that exact wording. Gloty still does not queue alt text for translation — that would spend your quota on per-product image descriptions — but where the same words appear in a heading you have already translated, the image now matches the page instead of staying in English.

1.56.0

  • New: the names of the products you sell are protected from translation as well as your brands. A fragrance called “Royal Oud” was coming back as “Decantación Real de Oud” in Spanish search results; product names now build the do-not-translate list automatically, and follow along as you publish, rename or unpublish.
  • Discovery sets, bundles, samplers and gift sets are deliberately left translatable: a name like “Sweet Addictions Set For Her” describes what is in the box, and shoppers should read it in their own language. Add a rule by hand if you want one of them frozen.
  • A protected product name is still only kept where it is capitalised, so “royal oud accords” in your notes copy keeps translating normally.

1.55.1

  • A protected term is now only kept inside a sentence when it is capitalised there, so a product name that is also an everyday phrase — “Side Effect” — no longer freezes “that side effect” in the middle of translated copy. Write the rule in lower case if you do want the lower-case form kept.

1.55.0

  • New: brand and product names you never want translated are now protected inside a sentence, not only when they are the whole string. A page title like “Royal Oud Decant – Creed” kept the brand in the glossary and still came back translated; it no longer can.
  • New: the do-not-translate list builds itself from your store. Every brand in your WooCommerce brand taxonomy, and your own site name, are protected automatically, and the list follows along when you add, rename or remove a brand. Terms you add by hand are never touched.
  • Fixed: on sites with more than a few thousand translated template strings per language, some of them quietly rendered in the original language. The serve cache kept an arbitrary slice of the available translations instead of all of them.

1.54.4

  • Fixed: an old link to a post or product whose slug has since changed now redirects to its current address in every language, as it already did in the default language. Under a language prefix it used to show a 404.
  • Show translations with ampersands and other HTML entities decoded in the Translations table and on the dashboard, as their originals already were.

1.54.3

  • Keep the existing translation cache when the server cannot finish writing its replacement.

1.54.2

  • Keep WP Shelf navigation and action cards within the screen on mobile, including Gloty’s setup and dashboard.
  • Match Gloty’s light-mode accent to its blue product icon.
  • Correct connection-error guidance to WP Shelf → Gloty → Setup.

1.54.1

  • Connect an existing WP Shelf account directly during setup with its license key.
  • Retry an interrupted site connection without creating a second account.
  • Verify the activated license when registering a translator connection, and report incomplete connections accurately.

1.54.0

  • Shared JavaScript search, sorting and pagination for admin data tables.
  • Preserve inline edits and selection scope while filtering loaded rows.

1.53.7

  • Fixed: a sync job the translation service no longer knows — it answers “not found” — stayed at “processing” for good, asked about again every five minutes. It is now marked failed, with the reason, the first time the service says so.

1.53.6

  • Fixed: the close button on a notification was labelled in English whatever language the site runs in. It is translatable now.

1.53.5

  • Accessibility: the column headers of every table in the admin — translations, sync jobs, the glossary, the diagnostics log and the loading skeletons — now announce themselves as column headers to screen readers.

1.53.4

  • Changed: the usage bar on the License panel now announces its percentage to screen readers, and its label is one translatable sentence rather than pieces.

1.53.3

  • Fixed: the CSV export (wp gloty export --format=csv) could carry a cell that a spreadsheet program treats as a formula. A source string or a translation beginning with a dash, a plus, an equals sign or an at sign — “- Read more” is enough — was evaluated by Excel or LibreOffice rather than shown, and a formula can open a link or call out of the program. Such cells are now written with a leading quote, which every spreadsheet reads as “this is text”, and the import removes that quote again so a translation that really begins with a dash is stored as written.

1.53.2

  • Fixed: Gloty’s inner screens returned “Sorry, you are not allowed to access this page”. Introduced in the previous release by an attempt to keep the WP Shelf menu highlighted; that attempt has been withdrawn. If you are on the previous version, update.
  • Known: the WP Shelf menu still shows as collapsed while you are on one of those inner screens. It is only the menu’s appearance — every screen and link works, and the plugin’s own sidebar shows where you are.

1.53.1

  • Fixed: in the dropdown switcher, the flag on the row with the longest language name was squashed to a sliver — it looked like one language had a broken icon. The menu now sizes itself to its widest language instead of to the button that opens it, and flags never shrink.

1.53.0

  • Added: “Footer bar” is now one of the switcher positions in Settings → Language Switcher. It puts the switcher in a strip at the end of the page instead of floating it over a corner, and it renders in whichever style you have chosen — including a dropdown, which keeps a footer with several languages down to a single control.
  • Changed: the footer strip follows the Style setting. If you turned it on with the gloty_switcher_footer_list option before this release it always rendered a flat list of links; it now shows a dropdown unless Style is set to Inline Links or Flags Only. The option still works and needs no change.
  • Improved: the switcher’s dropdown closes when you click elsewhere on the page or press Escape. It stays a plain list of links underneath, so it still opens, closes and reads correctly with JavaScript unavailable.

1.52.0

  • Changed: Gloty now sits under a single “WP Shelf” menu in your admin sidebar, alongside any other WP Shelf plugin you have installed, instead of taking a top-level spot of its own. If Gloty is the only one you run, you will find it at WP Shelf → Gloty. Every screen is exactly where it was inside the plugin, and every bookmark and link still works.
  • Fixed: on a phone or a narrow window, the sidebar inside Gloty’s screens is no longer hidden — it moves above the content instead. It used to disappear, on the assumption that WordPress’s own menu carried the same links.

1.51.0

  • Added: an Analytics screen showing how many page views each of your languages gets, over the last 7, 30 or 90 days, with each language’s share of the total. It answers the question the plugin could not before: is the German version worth what it costs?
  • The counting is local and collects nothing about anybody. No IP addresses, no page addresses, no user agents, no cookies and no accounts are stored — the database holds a number per language per day, and nothing is sent anywhere. Counting runs after the page has been delivered, so it adds nothing to how fast your site feels.
  • Two things the numbers do not include, both stated on the screen itself: views, not visitors (telling people apart needs a cookie, which this deliberately does not set), and pages served from a full-page cache such as WP Rocket or LiteSpeed, which never reach WordPress and cannot be counted. Your real totals are higher.

1.50.1

  • Fixed: the Gloty admin screen showed “There …