- Can I use fsi/admin-translatable-bundle in a Laravel application?
- No. This is a Symfony bundle that extends FSiAdminBundle, a Symfony admin generator, and hooks its form-event pipeline. It assumes Doctrine ORM entities implementing KnpLabs/DoctrineBehaviors Translatable or Gedmo Translatable, and none of those primitives exist in Laravel. Stack fit is effectively zero as a library; it is only useful to Laravel developers as a design reference.
- What does fsi/admin-translatable-bundle actually do?
- It adds a translation management layer to Symfony admin panels, giving editors a locale switcher and per-locale field editing inside existing admin forms. Messages are organised by locale and domain so teams can review and update multilingual content from one backend instead of editing translation files by hand. It is a thin form-layer extension, not a standalone translation storage or routing system.
- How do I install fsi/admin-translatable-bundle and what does it require?
- You install it with Composer, but the real commitment is FSiAdminBundle itself, which must be installed, configured and wired into your Symfony application first. The bundle expects the FSiAdminBundle asset pipeline, Doctrine ORM entities and a Translatable behaviour such as KnpLabs/DoctrineBehaviors. There is no path to using it standalone, and you should pin a specific commit rather than a version range.
- Which PHP, Symfony and Doctrine versions does fsi/admin-translatable-bundle support?
- The last release was in March 2020, targeting Symfony 3.4 and 4.x with PHP 7.x, Doctrine ORM 2.x and KnpLabs/DoctrineBehaviors 1.x. Expect deprecation noise and breakage on PHP 8.1 and later, plus incompatibility with modern Symfony 6 and 7 releases. Laravel 10 or 11 is incompatible by construction, not by configuration.
- Is fsi/admin-translatable-bundle still maintained and safe for production?
- There has been no upstream activity since March 2020, and the repository has zero stars and zero dependents. Zero dependents is the material signal: there are no production canaries, no downstream bug reports and no evidence the code works outside its author's applications. Adoption equals ownership, so budget a permanent in-house fork or a scheduled replacement from day one.
- What are the risks of adding this bundle as a Composer dependency?
- Installing it pulls FSiAdminBundle, its asset pipeline and Symfony 3.4/4.x-era components into your dependency graph, all of which will accumulate security advisories faster than a small team can track. Provenance risk is high and concentrated: single-vendor origin, zero dependents and no issue triage. Internal code review is the only safety net, and there is no vendor or community support to escalate to.
- What Laravel alternatives exist for managing translations in an admin panel?
- For Laravel, look at packages such as spatie/laravel-translation-loader for database-backed translations, astrotomic/laravel-translatable for per-model translation tables, and mcamara/laravel-localization or laravel-lang for locale handling. None of them replicate the admin UI, so you pair one with a Filament or Nova resource, or a small Livewire screen. That combination is a smaller and better-supported commitment than porting a Symfony admin bundle.
- How would I implement locale-tab translation editing natively in Laravel?
- Store translations in a JSON column or an entity_translations side table, then validate with a FormRequest covering translations.{locale}.{field}. Build a Blade or Livewire partial with a locale tab strip, per-locale fields, fallback-locale highlighting, and a single submit that persists every locale at once. The transferable ideas from this bundle are exactly that: the switcher UX and the form-to-translation data mapping.
- Do I need this bundle if I only want to switch the admin's active locale?
- No. Switching the admin's active locale is a much smaller requirement than editing every locale in a single form, and only the latter justifies studying this code. For a locale switcher you can store the preference in the session or user record and set the application locale from middleware in a few dozen lines. Keep the scope decision explicit before you pull any dependency into the graph.
- How should I evaluate or test fsi/admin-translatable-bundle before adopting it?
- Read the source first, since it is small, and write a short design note capturing the locale switcher UX and the form-to-translation data mapping. Reproduce the pattern in a throwaway Laravel spike with your real storage model, and only vendor the bundle itself if your target is genuinely Symfony with FSiAdminBundle. Any plan whose first step is composer require is a plan that stalls.