Weave Code
Localisation Laravel Package
laravel-enso/localisation
Laravel Enso Localisation provides language and translation management for Enso-powered Laravel applications. It includes models, migrations, and an admin interface for configuring locales and maintaining translation strings, making multilingual apps easier to manage.
Laravel Enso Localisation package, meant to make it easy to build an application and offer it in multiple language versions
Frequently asked questions about Localisation
- What is laravel-enso/localisation used for?
- It is a localisation module for Laravel applications built on the Enso framework. It provides locale records, migration files, relational translation tables, locale-resolution middleware, and an admin interface for maintaining translation strings. In practice it lets an Enso app serve its content and UI in multiple languages without writing custom i18n code.
- Does laravel-enso/localisation work in a standard Laravel app without Enso?
- No, not realistically. The package has a hard dependency on enso/core and expects your models to follow Enso conventions, so adopting it means adopting the Enso substrate. If you are not already standardising on Enso, pick a standalone translation package instead. Use Enso adoption at the platform level as the gate for this decision.
- Which Laravel and PHP versions does laravel-enso/localisation support?
- The last release was published in November 2020, so it most likely targets Laravel 6 through 8 and PHP 7.3 or 7.4. Treat Laravel 10, 11, and PHP 8.1+ as unsupported until you confirm the constraints in composer.json. Pin exact versions of both enso/core and this package, and commit your composer.lock.
- How do I install laravel-enso/localisation?
- Installation is Composer-based: require the package, which pulls in enso/core as a dependency, then publish its config and run its migrations. The install itself is quick; the real cost is the prerequisite Enso core setup, database conventions, and optionally the Vue front-end. Always run the migrations against a staging database first and diff the resulting schema.
- Are translations stored in lang files or in the database?
- Enso stores content translations in relational translation tables rather than in Laravel's lang/ files. That means per-record multilingual content lives alongside your models and is queried through Eloquent. Plan your content migration accordingly, because file-based translation workflows do not map directly onto this schema.
- Do I need Enso's Vue front-end to use laravel-enso/localisation?
- Not necessarily, but it depends on how much of the package you use. The locale and translation models, migrations, and middleware are backend concerns, while the admin screens for managing locales and strings ship as Enso UI components. If you skip the UI you will need to manage locale and translation records yourself, so confirm headless usage during a spike.
- What are the best alternatives to laravel-enso/localisation?
- For a conventional Laravel application, spatie/laravel-translation-loader, astrotomic/laravel-translatable, and mcamara/laravel-localization cover comparable ground. They deliver database or file-based translations, per-model translated attributes, and locale routing without pulling in Enso. Choose this package only when the Enso ecosystem is already your application framework.
- Is laravel-enso/localisation actively maintained?
- Activity is low: the last release was in November 2020 and the repository has only a small star count, indicating a thin community around it. Continuity risk sits with the wider Enso project and its single-maintainer structure rather than this package alone. The MIT licence is clean, so forking and maintaining internally is a viable fallback if upstream goes quiet.
- How should I migrate existing multilingual content into this package?
- Do not start by migrating content. First confirm Enso adoption, pin the package versions, install and run migrations in staging, seed the locale set, and validate fallback behaviour end to end. Then move one low-risk module such as static pages or categories, backfill with an idempotent scripted importer, and keep the source data until parity is verified.
- How can I validate laravel-enso/localisation before committing to it?
- Run a short, time-boxed spike on a throwaway branch: install the package, translate one model, exercise a locale switch, and check that the UI renders translated content if you plan to use it. Only fund the wider migration if that spike passes cleanly on your target Laravel and PHP versions. Also decide up front who would own an internal fork.
Weaver
How can I help you explore Laravel packages today?