Translation Bliss: Simplified Translations, Total Control
Translation Bliss simplifies multilingual Drupal site management by providing a unified configuration translation system, language selectors for config forms, and flexible source language options. It also includes tools for exporting and importing all translatable strings for Git-friendly workflows and bulk correction of configuration language codes.
Managing a multilingual Drupal site shouldn't require a translation specialist just to understand why a button label is showing up in the wrong language. Translation Bliss makes translation predictable and auditable.
Features
Capability What it solves Unified config translation Auto-translates all config using UI translations, with per-context overrides. No more manually hunting through config translation forms. Config language widget Adds alangcode selector to every config form, so you always know โ and can control โ which language a config entity belongs to.
Source language flexibility
Define translation contexts from any source language. Ideal for sites originally built in German, French, Arabic, or any non-English language.
Total translation export/import
drush tex exports all module and custom translatable strings + translations into a structured directory. drush tim imports them back. Everything is git-friendly.
Bulk langcode conversion
Drush commands to diagnose and batch-correct config langcode values across an entire site โ a lifesaver when migrating or auditing legacy multilingual setups.
๐ See Translation Bliss Documentation
Translation & Deployment Workflow
Here is a typical workflow for a multilingual site with English (source), German, and French:
1. Build and configure locally Build your site.
2. Export all translations
drush tex --destination=./translationsThis exports every translatable string โ including config labels, field names, views headers, and custom strings.
3. Translate The ./translations directory is handed to translators (or a translation service). PO files are edited directly, or processed through a CAT tool. Changes are committed to the git repository.
4. Review and deploy On deploy:
drush tim --source=./translationsTranslations are imported cleanly into the target environment. No database-only translation state. No drift.
5. Fix a config langcode issue discovered on staging
drush translation-bliss:diagnose drush translation-bliss:convert-langcodes --bundle=node --langcode=en
Bulk corrections applied, committed, and deployed โ no manual clicking through admin UIs.
Consulting, training and coding for complex drupal projects. With 20 years of drupal coding and compelling contributions, we hook in when it gets dicey.
Depends on
Dependencies of the latest stable release
No dependencies recorded for this project.
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.
Activity
Release Timeline
Releases
| Version | Type | Core | Notes | Release date | |
|---|---|---|---|---|---|
| 1.0.0-alpha17 | Pre-release | 10โ11 | May 18, 2026 | ||
| 1.0.0-alpha16 | Pre-release | 10โ11 | Oct 11, 2025 | ||
| 1.0.0-alpha15 | Pre-release | 10โ11 | Sep 29, 2025 | ||
| 1.0.0-alpha14 | Pre-release | 10โ11 | Aug 29, 2025 | ||
| 1.0.0-alpha13 | Pre-release | 10โ11 | Aug 28, 2025 | ||
| 1.0.0-alpha12 | Pre-release | 10โ11 | Jan 31, 2025 | ||
| 1.0.0-alpha11 | Pre-release | 10โ11 | Jan 30, 2025 | ||
| 1.0.0-alpha10 | Pre-release | 10โ11 | Oct 23, 2024 | ||
| 1.0.0-alpha9 | Pre-release | 10โ11 | Oct 14, 2024 | ||
| 1.0.0-alpha8 | Pre-release | 10โ11 | Oct 1, 2024 | ||
| 1.0.0-alpha7 | Pre-release | 10โ11 | Oct 1, 2024 | ||
| 1.0.0-alpha6 | Pre-release | 10โ11 | Oct 1, 2024 |