Weave Code
Lexik Translation Ui Bundle Laravel Package
forci/lexik-translation-ui-bundle
Provides a web interface for managing translations with LexikTranslationBundle, letting teams browse, edit, and organize translation messages from a single dashboard. Ideal for Symfony apps that need a lightweight translation admin UI.
UI for LexikTranslationBundle
Frequently asked questions about Lexik Translation Ui Bundle
- Is forci/lexik-translation-ui-bundle a Laravel package?
- No. It is a Symfony bundle that bootstraps through a Bundle class, a DI extension, and compiler passes, and it depends on Symfony's HttpKernel, Twig, Form, Security, and Doctrine ORM/DBAL. Laravel has no bundle loader, no Twig by default, and no Doctrine entity manager, so the framework layers do not line up. Only the domain concept, not the code, is reusable in a Laravel app.
- Can I install forci/lexik-translation-ui-bundle in a Laravel app with Composer?
- There is no realistic path to composer require this into a Laravel application and have it work. Composer may resolve the dependency, but Laravel will not boot the bundle, register its routes, or render its Twig views, and it has no Doctrine entity manager for the translation entities. Your options are to port the concept natively to Laravel, use an off-the-shelf Laravel translation manager or Filament resource, or run the bundle as a small sidecar Symfony app against the same database behind an internal host or SSO proxy.
- What does this translation UI bundle actually do?
- It provides a web interface for managing translations with LexikTranslationBundle, letting teams browse, edit, and organize translation messages from a single dashboard. It typically adds import and export to files and cache invalidation on write. It is aimed at Symfony applications that need a lightweight translation admin UI rather than a full localization platform.
- Which Laravel versions does forci/lexik-translation-ui-bundle support?
- None, because it is not a Laravel package and declares no Laravel version support. Its compatibility is defined by Symfony component constraints in composer.json and by the upstream LexikTranslationBundle version it was forked from. In a Laravel context you would rebuild the feature rather than rely on this bundle's version matrix.
- What is the best Laravel alternative for a translation admin UI?
- spatie/laravel-translation-loader already implements DB-first translation loading with file fallback, which is the core runtime piece you would otherwise write yourself. For the editing screen, a Filament, Nova, or Backpack resource over a translations table gets you a working CRUD grid quickly. Below roughly 5k keys a naive paginated grid is fine; above that you need pagination and virtualization on the grid queries. Choose based on your existing admin surface, key count, and import/export requirements.
- How do I port the Lexik translation UI concept to Laravel natively?
- Create a translations table with domain, locale, key, value, and timestamps, then backfill it from your existing lang files. Register a DB-backed loader decorator, or use spatie/laravel-translation-loader, so runtime lookups resolve cache-then-DB-then-file. Add cache flushing on save, build the editing screen behind a permission gate, and add import/export plus an audit trail. Realistically this is 3 to 10 days of work, but you own every line and avoid a second runtime.
- How should DB translations and lang files interact, especially with import and export?
- Decide and document an explicit precedence rule, because the bundle's model is a domain, locale, key, translation row set with file import and export. In Laravel, a loader decorator or spatie/laravel-translation-loader lets you resolve cache first, then the database, then files, so file-based lang files can remain the fallback or the source of truth. Backfill lang files into the table at the start and keep a rollback story so a bad import cannot leave you without copy.
- How do I cache database translations and invalidate the cache on save?
- Cache lookups so runtime resolution is cache-then-DB-then-file, and never hit the table on every __() call. On save, flush either per-locale cache keys or tagged cache entries, and make the flush part of the same write path so editors cannot save without invalidating. If you run the Symfony UI as a sidecar, remember there are two caches to invalidate, so write the invalidation contract down explicitly.
- How do I test a database-backed translation loader in Laravel?
- Use RefreshDatabase, seed a few rows into the translations table, clear the translation cache, and assert that __() returns the database value. Then remove the row or query a missing key and assert the fallback to lang files still works. Add a round-trip test for import and export so a bad parser or writer is caught before it reaches production copy. Clear the cache in setUp or tearDown to avoid order-dependent failures.
- Is it safe to adopt this bundle given its license and maintenance status?
- Treat it as high risk. GitHub reports zero stars, zero dependents, and a NOASSERTION license, which is a hard gate: read the LICENSE file and diff it against upstream Lexik, which is MIT, before shipping or redistributing anything. It is also a single-maintainer fork with no security disclosure channel and no release cadence, and the fork may already be stale against upstream. Assume you become the maintainer the moment you adopt it.
Weaver
How can I help you explore Laravel packages today?