Weave Code
Filament Translatable Laravel Package
filamerce/filament-translatable
Filament Translatable brings multilingual editing to Filament resources, letting you manage translated fields across locales with locale switchers, per-language inputs, and smooth integration with translatable models. Simplify multilingual admin panels and keep translations organized.
Highly customizable Translation component for FilamentPHP
Frequently asked questions about Filament Translatable
- What is filamerce/filament-translatable used for?
- It is a Filament panel plugin that adds multilingual field authoring to resources, with locale switchers and per-language inputs layered over a Laravel translation backend such as spatie/laravel-translatable. It owns only the presentation layer of translated editing and delegates persistence to a translation trait on your Eloquent model. It fits teams whose admin panel is the primary authoring surface and who work with two or more content locales.
- How do I install filament-translatable in a Laravel Filament application?
- Run composer require filamerce/filament-translatable, register the plugin on your Filament panel, add the translation trait and a $translatable array to the model, then declare translatable fields in your resource schema. On a greenfield project or one already running Filament v5 this is a same-day task. On an existing Filament v4 codebase the install is coupled to a panel-wide v5 upgrade.
- Does filament-translatable v3.2.0 support Filament v5 and Filament v4?
- The v3.2.0 release notes state Filament v5 compatibility but do not publish a constraint matrix, so whether v4 remains in the composer.json range is unconfirmed. Three scenarios are possible: v4 support was dropped and existing installs break on composer update, both majors are supported via widened constraints, or v5 is the floor and v3.1.x is the v4 branch. Pin your version and inspect the composer.json constraints before updating.
- Which PHP and Laravel versions does filament-translatable require?
- The v3.2.0 release notes do not include a minimum PHP or Laravel version statement, so the README and composer.json are the authoritative source. Check the constraints on php, laravel/framework, filament/filament and your translation backend before adopting. Given the missing compatibility matrix, this is worth confirming directly with the maintainer.
- Does filament-translatable work with spatie/laravel-translatable?
- Yes, spatie/laravel-translatable is the most common backend, and the plugin delegates persistence to the model trait rather than owning translation storage. Whether custom trait implementations are covered by the test suite is not documented. Verify that your specific backend resolves fields correctly before a wide rollout.
- How do I register the filament-translatable plugin on a Filament panel?
- Register the plugin in your panel's plugin array, typically inside a PanelProvider, after which the translatable form and table components are available in your resource schemas. The exact registration surface follows Filament's plugin API for your installed panel version. The README covers the base setup steps.
- Can I use it with column-per-locale or custom JSON translation storage?
- The package is built for the trait-based translatable contract, so a bespoke column-per-locale or custom JSON resolution scheme may not render as expected. Evaluate whether the field components still behave correctly with your storage layer, or whether a thin in-house wrapper is cheaper than adapting. Confirm your storage strategy before committing to adoption.
- What is the migration path from Filament v4 to v5 when using this package?
- No migration guide for v4 to v5 was published with v3.2.0, and the v5 move is a panel-wide upgrade involving schema and action namespace changes, asset and theming updates, and plugin registration. A minor version number is being used to signal a major platform dependency shift, so constrain the package version in composer. Ask the maintainer for a documented support window for the 3.1.x line.
- Is filament-translatable well tested, and are locale fallback and validation handled?
- The release notes contain no test evidence, and coverage across the v4 and v5 matrix is unknown. Locale fallback and validation edge cases in translatable forms are historically where these plugins accumulate defects. Test required-field validation, fallback display and partially translated records in your own environment before production.
- What are the alternatives to filament-translatable and is it actively maintained?
- Alternatives include a thin in-house wrapper over your translation trait or other Filament translation plugins. This is a single-maintainer project with a small contributor base and no published release cadence or LTS policy, which is a real consideration for long-lived admin panels. For teams already standardised on Filament with trait-based storage it remains a reasonable fit.
Weaver
How can I help you explore Laravel packages today?