Weave Code
Nova Locale Manager Laravel Package
outl1ne/nova-locale-manager
A Laravel Nova tool and resource for managing your application's locales and languages from the admin panel. Add, edit, enable or disable locales and set the default language without touching configuration files, keeping multilingual projects simple to maintain.
An extremely simple Laravel Nova tool for managing locales.
Frequently asked questions about Nova Locale Manager
- Do I need Laravel Nova to use outl1ne/nova-locale-manager?
- Yes. It is a Nova tool, so it only works inside a Laravel application with a licensed Nova installation. Nova is a paid product licensed per project, so the real cost decision is Nova itself, not this package. If you use Filament, Backpack, or a custom admin panel, this package is not usable there.
- How do I install outl1ne/nova-locale-manager?
- Run composer require outl1ne/nova-locale-manager, then register the tool in your NovaServiceProvider tools() method. Publish and run the package migration, and optionally seed your current locale set so behavior matches your existing config. Do this on a scratch branch first to catch Composer constraint conflicts.
- Which Laravel and Nova versions does this package support?
- The last release was July 2022, so expect Composer constraints aimed at Laravel 8/9 and Nova 3/4-era versions. Support for Laravel 10+ and newer Nova releases is not verified, so check the declared constraints before planning an upgrade. If you are on a current Laravel and Nova stack, test installation in a throwaway branch or vendor the small screen yourself.
- Does it create the locales table or expect an existing one?
- It ships its own migration and model for a locales table, which you publish and run during setup. If your application already has a locales table, review the schema before migrating to avoid column or index conflicts. Decide whether the package table becomes the single source of truth or is adapted to your existing structure.
- How do I make my Laravel app read locales from the database instead of config?
- The package only manages locale records; it does not rewire your translation loader, route middleware, caches, or sitemap generator. Inventory every consumer of locale data, then cut them over to the database-backed list explicitly. That cutover is the real migration and is usually larger than installing the tool.
- Is outl1ne/nova-locale-manager maintained and safe for production?
- Maintenance is thin: around sixteen stars and a last release in July 2022 place it in the low-activity, possibly orphaned category. Its surface area is genuinely small, so the fallback is strong: a developer can vendor or reimplement the screen in a day or two. Treat it as a tactical convenience, not a load-bearing dependency, and pin versions. The license is MIT, so there is no legal or redistribution friction.
- What happens to translated content when a locale is deleted through the tool?
- The tool provides standard Nova resource CRUD, so deletion behaves like any other resource delete. It does not know about your translated content, relationships, or fallback rules, which means silent orphaning is possible. Add soft deletes, block deletion when content exists, or cascade cleanup, and verify the behavior in staging.
- Does the package invalidate caches when locales change?
- Cache integration is not documented, so do not assume the tool clears your locale list or translation caches on write. If you cache locales for routing, hreflang, or sitemaps, add model observers or explicit cache invalidation. Confirm the behavior after every create, update, enable or disable, and delete.
- Can I use this locale manager with Filament or a custom admin panel?
- No. It is built specifically as a Laravel Nova tool and is not portable across admin frameworks. Teams on Filament, Backpack, or custom panels should build a small resource or use an admin-panel-native locale manager instead. The underlying CRUD is simple enough that porting the idea is straightforward.
- How do I set or change the default locale and enable or disable languages?
- The Nova resource lets you edit locale records, toggle enabled status, and set the default language from the admin panel. Enforce a single default at the application level and make sure every consumer resolves from the same source of truth. Also confirm the tool respects Nova authorization gates so only intended administrators can change locale state.
Weaver
How can I help you explore Laravel packages today?