Weave Code
Filament Astrotomic Laravel Package
fnx-software/filament-astrotomic
A Filament plugin for Astrotomic Translatable models that simplifies multilingual content management. Edit translations directly in Filament forms and tables with locale-aware fields, tabs, and validation, reducing custom code and making translated records easy to maintain across your admin panel.
Manage multilingual content in Filament v4 & v5+ with astrotomic/laravel-translatable, supercharged with a reactive Locale Switcher, sortable/searchable Columns, and a translatable Select component.
Frequently asked questions about Filament Astrotomic
- How do I install fnx-software/filament-astrotomic in a Laravel Filament app?
- Install it with Composer using composer require fnx-software/filament-astrotomic, then register the plugin in the appropriate Filament panel provider according to the package documentation. Confirm your PHP, Laravel, Filament, and astrotomic/laravel-translatable versions satisfy the package constraints before installing. Your models should already use Astrotomic Translatable and store translated attributes in related translation tables.
- Which Filament versions does this package support?
- The package targets Filament v4 and v5+ admin panels in Laravel applications. Because Filament major versions can change form and table APIs, always check the Composer constraints and release notes for the exact supported versions. Confirm compatibility in a branch before upgrading production panels.
- Does it work with astrotomic/laravel-translatable models?
- Yes. It is built for models managed by astrotomic/laravel-translatable, where translated attributes live in a related translation table. The package expects the related models to expose the expected translation API, such as translate($locale), so validate that contract in your models. It is intended for the Filament presentation and form layer rather than as a domain-layer dependency.
- Do I need to change my database schema or run migrations to use it?
- No data migration is expected from the v2.1.0 release, and the package is designed for existing normalized translation schemas. You should still confirm your translated models and relationships match Astrotomic conventions before adoption. If you change label or search behavior, add regression tests rather than altering stored data.
- How does the Locale Switcher work in Filament forms?
- The Locale Switcher provides a reactive way to change the active locale while editing multilingual content in Filament forms. It supports locale-aware fields, tabs, and validation so editors can work on translations without custom form code. Test how your configured fallback locale behaves when a translation is missing for the selected locale.
- How do I show translated values in Filament tables?
- Use the package's TranslatableColumn to display locale-aware translated values in Filament tables, with support for sortable and searchable columns. The column resolves translations for the active locale, reducing custom table formatting. For detail views, TranslatableEntry remains available and is unchanged in the v2.1.0 release.
- Can TranslatableSelect search translated relationship labels?
- In v2.1.0, TranslatableSelect resolves relationship option labels and search results through translated records instead of assuming translated attributes exist on the base table. This fixes SQL failures when translated attributes live only in translation tables. Use translatableLabelUsing() for composite labels and translatableSearchAttributes() for multi-attribute search, and verify whether your configuration searches the active locale only or includes fallbacks.
- What happens when a translation is missing for the active locale?
- Missing translations may appear as empty labels or fall back to another locale depending on your Astrotomic and Filament configuration. Verify fallback settings and add tests for records that lack a translation in the active locale. This is especially important for select option labels and searchable translated fields.
- Is it safe to upgrade existing TranslatableSelect usage to v2.1.0?
- It is intended as a low-friction Composer upgrade: translatableRelationship() and modifyQueryUsing are preserved, while translatableLabelUsing() and translatableSearchAttributes() are opt-in. No documented breaking change is called out, but relationship label and search resolution changed, so regression testing is important. Inspect existing TranslatableSelect fields and any local subclasses or custom option-label logic.
- How should I test and benchmark the package for production?
- Add regression tests for the previously failing SQL scenario where translated attributes exist only in the translation table. Then cover composite labels, active-locale search, missing translations, fallback behavior, and modifyQueryUsing callbacks. For large related tables, benchmark searchable() and preload() behavior in staging because multi-attribute search and per-record translation access can add query complexity.
Weaver
How can I help you explore Laravel packages today?