Translingua

Initial release.

Added

Static translations (Lite)

• Static translation editor for template strings, scanned from |t, Craft::t() and Craft.t() calls across templates, modules and local plugins.
• Language file overrides for any installed plugin that ships translations, plus Craft's own control panel strings. Strings a plugin already translates are shown pre-filled and marked as defaults; editing one turns it into a project override.
• Formie translations, editable from the control panel.
• Add, edit and delete individual strings, with search, a missing/translated filter and pagination for large sets. Strings carrying meaningful leading or trailing whitespace are outlined.
• Scan results are cached against the modification times of the files they were read from, so an unchanged project never pays for a rescan. A Rescan templates button forces one.
• Everything is written to translations/{locale}/{category}.php — vendor/ is never modified.

AI translations (Pro)

• AI translations through DeepL, OpenAI, Anthropic (Claude) or Google Gemini, using your own API key. Keys support environment variables.
• A translate button on every text input in the control panel, including CKEditor, and inside other plugins' screens such as Formie and SEOmatic — the buttons read the DOM rather than knowing about specific field types.
• A Translate page button next to Save, limited to entry, category and global set edit screens plus SEOmatic's Global SEO and Content SEO. Configurable via the pageButtonPaths setting.
• Batch translation of entries, categories and global sets from one site into any number of others, on the queue, with per-field selection that reaches into Matrix blocks. Fields whose translation method is none are shown but disabled, since Craft stores one value for every site.
• Optionally creates a revision before each batch write, so a run can be rolled back from the element's revision menu.
• A Translingua tab in Formie's form builder: set the language the form is written in, and translate the whole form server-side. Field handles, option values, CSS classes and input attributes are never translated.
• A Translingua toggle on each section, category group and global set's own settings screen, governing every feature for that source.
• Identical strings are cached for a month, so re-running a batch costs nothing for anything already translated.
• Console commands for listing sources, scanning templates and running batch translations.

Security

• Two user permissions are registered — Manage static translations and Use AI translations. Plugin settings remain admin-only.
• The translate buttons only appear once a real request to the provider has succeeded, so a wrong, expired or out-of-quota key means no buttons rather than failures at the point of use.
• URLs, paths, email addresses, phone numbers, bare numbers and Craft's own revision notes are never sent to the translation provider, whatever the field is called. Link fields pointing at an email address, phone number or SMS number are left alone entirely.
• No translate buttons are loaded at all on Settings, the Plugin Store, Utilities, Updates, user accounts or plugin configuration screens.
• Nothing is ever saved on your behalf: translations land in the input and you press Save.