Download the PHP package asignua/filament-translatable-fields without Composer

Filament Translatable Fields

Per-field language tabs for spatie/laravel-translatable in Filament 5. Every language is a real input in the form state at the same time, so translations survive a Repeater, a Builder, a ->relationship() repeater and a settings page.

Filament's official translatable plugin was discontinued after v3, and the replacements switch ONE global locale for the whole form. That is exactly what breaks nested fields: the order and the data of a repeater are lost after the editor switches language (filamentphp/filament#8328, plus dozens of help threads and ideas about repeaters, builders, relationships and settings pages). Here there is no global locale: each translatable field carries its own tabs and its own title.uk / title.en state.

• Screenshots
• Requirements
• Installation
• Usage
• Repeaters, builders, relationships, settings pages
• Saving
• Tables and infolists
• Configuration
• Gotchas
• Translations
• AI agents
• Testing

Screenshots

Requirements

• PHP 8.3+
• Laravel 12 or 13
• Filament 5
• spatie/laravel-translatable ^6.11 (installed as a dependency)

Installation

There is no panel plugin to register and no asset to publish: the package is plain Filament components. Optionally publish the config:

Your model uses spatie as usual:

Usage

The factory component keeps the attribute name (title); the plugin binds it to title.{locale}. Inside the tabs:

A tab whose input (or anything inside it, e.g. a repeater in a language tab) has a validation error gets a red ! badge. Error messages name the language (Title (English)).

Repeaters, builders, relationships, settings pages

Nothing special — put the component where the field goes:

On a page without a model (settings in a table, a cache, a config file) the state is simply an array: ->fill(['site_name' => ['uk' => '…', 'en' => '…']]) and $this->form->getState() returns the same shape.

How it decides where the value comes from: whatever was passed to fill() wins. EditRecord and a ->relationship() repeater fill the form from attributesToArray(), which already holds the whole map, so a change made in mutateFormDataBeforeFill() stays. Only when {field} did not arrive as an array — or when the form is filled with no data at all (a record Action's default mount, a custom page with ->record($record) and fill()) — are the languages read from $record->getTranslation($field, $locale, false), and only when the field sits directly in the schema that was given that record. The record is read before the language inputs hydrate, so their own afterStateHydrated() hooks receive the record's value. A JSON repeater/builder item, or a group with its own statePath(), is never read from the record — so an item field called title is never overwritten by the record's own title.

Saving

Filament's default save already works with spatie: $model->fill(['title' => ['uk' => 'a', 'en' => 'b']]) calls setTranslations(), and a cleared language ('en' => null) is cleared. You do not need anything else for a normal model. The optional page trait is a helper for the rest:

• fillTranslations($record, $data, forgetEmpty: false) writes the maps with setTranslation() and returns the rest of $data — for models with $guarded = ['*'] where fill() writes nothing. forgetEmpty: true removes cleared languages from the JSON instead of storing ''.
• Its mutateFormDataBeforeCreate/Save() store a cleared language as '' instead of null (tidiness, not correctness). A locale key that is absent (a hidden or disabled input) is left untouched — spatie merges the languages it is given into the stored ones. A page that defines its own mutateFormDataBeforeSave() replaces the trait's: call $this->normalizeTranslatableData($data, $this->translatableModel()) there if you want it.

For the same normalisation outside a page: TranslatableFields::normalize($data, ['title', 'body']).

Tables and infolists

The value of the current language; if it is empty, the default language, then any filled one, prefixed with a marker ([en] Hello) so an editor can tell a borrowed text from a translated one. Nothing is written back. Use them in the admin only — [en] in a public <title> is an SEO bug. searchAcrossLocales() searches title->uk, title->en, … case-insensitively — ilike on PostgreSQL, lower(…) like lower(?) on MySQL/MariaDB, plain like on SQLite (ASCII letters only); team.name searches through whereHas('team'). sortableByLocale() sorts by the shown text — the current language, then the default, then the rest — and works on the table's own attributes only (it throws for team.name). A cleared language (stored by spatie as JSON null) neither matches a search nor sorts as the text null: on MySQL/MariaDB it is mapped to SQL NULL and falls through to the next language.

Configuration

In code (for example AppServiceProvider::boot()), which wins over the config:

Gotchas

• Configure the languages. Without locales in the config or TranslatableFields::locales([...]), the plugin offers app.locale + app.fallback_locale (spatie/laravel-translatable has no language list of its own) — on a fresh Laravel app that is a single en tab.
• Your factory's own afterStateHydrated() is kept and runs after the plugin has read the record (see above), so it sees — and may change — the record's value for its language.
• Empty badges are opt-in (emptyBadges() or empty_badges => true) because they make the inputs live(onBlur: true) — one request per blur, which adds up on large forms — unless your factory already chose live().
• spatie hides '': getTranslations('title') omits languages stored as an empty string; read the raw column, or getTranslation($field, $locale, false), when you need to see exactly what was stored.
• No nested/dotted attribute names (meta.title): the attribute is the first state segment.
• The component name must match the attribute: make('title', fn () => TextInput::make('title')).
• Fields in a Section/Grid with the language tabs inside work; wrapping the tabs in a component that has its own statePath() makes the field belong to that array (no record lookup), which is what you want for JSON groups.

Translations

The interface ships in English, Ukrainian, German, Spanish, French, Italian, Dutch, Polish, Brazilian Portuguese and Turkish under the filament-translatable-fields::translatable-fields namespace; a test keeps every language in step.

AI agents

The package ships Laravel Boost guidelines (resources/boost/guidelines/core.blade.php).

Testing

The suite runs on Orchestra Testbench with a workbench/ resource (a model with translatable columns, a JSON Repeater, a Builder, a relationship Repeater) and a Livewire settings page.

Changelog

See CHANGELOG.md.

License

The MIT License (MIT). See LICENSE.md.