- How do I install 3x1io/filament-translations in a Laravel app?
- Install it with composer require 3x1io/filament-translations, then register the plugin class inside your Filament panel provider's plugin list. Publish the package config and any assets with the vendor:publish command referenced in the README. No schema migration is required for the default file-based mode, so installation is a composer step plus a panel registration. Expect a half-day spike to get it running in a non-production panel.
- Which Laravel and Filament versions does filament-translations support?
- The expected envelope is Laravel 10 or 11 with Filament v3 and PHP 8.1 or newer. Always check the installed composer.json constraints before merging, since the package tracks Filament form-component APIs and a Filament major upgrade can strand the plugin. Pin a minor range and re-test the plugin whenever you bump Filament.
- Does filament-translations store translations in the database or in lang files?
- By default the package reads and writes your application's lang/ files, which stay the source of truth. It is a thin UI layer rather than a translation storage model, so there is no implied schema migration for the standard file-based mode. Depending on configuration it can work against a database-backed loader, but you should confirm that behaviour against your setup before relying on it.
- How do I register the translations plugin in my Filament panel provider?
- Open the panel provider where your other plugins are registered, usually app/Providers/Filament/AdminPanelProvider.php, and add the package's plugin class to the plugins() array. Package auto-discovery handles the service provider, so no manual provider wiring is needed. Publish the config and assets, then load the panel to confirm the translations page appears.
- Does editing a translation in the admin panel clear Laravel's translation cache?
- This is one of the first things to verify in a staging environment, because edits made through the UI must invalidate or regenerate cached translations. If the cache is not cleared, admins will keep seeing stale strings even though the file on disk changed. Test an edit with cached translations enabled, and plan a cache:clear step or an event hook if the package does not handle it for you.
- Can filament-translations scan for missing translation keys?
- Yes, scanning for missing keys is one of the headline features alongside editing language files and switching locales. The scan compares the keys used in your app against those present in your lang files, which is useful before a release. Run it on staging first to gauge how long it takes with your key volume.
- Will scanning large lang directories slow down my Filament admin panel?
- Scanning large language directories on every page load can degrade the admin panel as key counts grow, so treat scan performance as a real risk rather than an edge case. Measure the scan time against a production-sized copy of your lang/ directory and consider triggering scans on demand instead of automatically. If your app has thousands of keys, cache or throttle the scan results.
- Is filament-translations compatible with spatie/laravel-translation-loader or a database translation source?
- The package is built around flat PHP and JSON lang files, so its write path can diverge from the source of truth when translations are owned by a database loader or a third-party TMS. Confirm during your spike whether the installed version respects a spatie/laravel-translation-loader-style DB source or hard-assumes files. If a TMS or database owns your translations, treat this plugin as a poorer fit.
- Is it safe to let the web process write to the lang directory?
- Filesystem write access from the web process into lang/ is a permissions and audit-trail question you should review before going live. Check whether writes are atomic and whether there is a backup or undo path if an edit goes wrong. Keeping translations committed to your repository gives you a rollback route and makes any accidental overwrite recoverable via version control.
- Is filament-translations actively maintained and safe to use in production?
- It is a single-maintainer package with a small contributor base, so technical risk is dominated by maintainership rather than code quality. Review the release cadence and issue-response history over the last 12 months before adopting it. The good news is that it is cleanly removable: because translations live in files you commit to the repo, removing the plugin is a composer remove rather than a data extraction exercise.