codezero/laravel-localizer

Automatically detect and set an app locale that matches your visitor's preference.

3.0.0 2024-03-11 13:44 UTC

Requires

• php: ^8.1
• codezero/browser-locale: ^3.0
• illuminate/support: ^10.0|^11.0

Requires (Dev)

• mockery/mockery: ^1.3.3
• orchestra/testbench: ^8.0|^9.0
• phpunit/phpunit: ^10.5

MIT

• Ivan Vermeyen

• php
• browser
• locale
• language
• detect
• session
• laravel
• localization
• cookie
• country

README

Automatically detect and set an app locale that matches your visitor's preference.

• Define your supported locales and match your visitor's preference
• Uses the most common locale detectors by default
• Uses the most common locale stores by default
• Easily create and add your own detectors and stores

✅ Requirements

• PHP >= 8.1
• Laravel >= 10.0

⬆ Upgrade

Upgrading to a new major version? Check our upgrade guide for instructions.

📦 Install

Install this package with Composer:

composer require codezero/laravel-localizer

Laravel will automatically register the ServiceProvider.

🧩 Add Middleware

By default, the app locale will always be what you configured in config/app.php. To automatically update the app locale, you need to register the middleware in the web middleware group. Make sure to add it after StartSession and before SubstituteBindings.

The order of the middleware is important if you are using localized route keys (translated slugs)! The session needs to be active when setting the locale, and the locale needs to be set when substituting the route bindings.

Laravel 11 and newer:

Add the middleware to the web middleware group in bootstrap/app.php.

// bootstrap/app.php
->withMiddleware(function (Middleware $middleware) {
    $middleware->web(remove: [
        \Illuminate\Routing\Middleware\SubstituteBindings::class,
    ]);
    $middleware->web(append: [
        \CodeZero\Localizer\Middleware\SetLocale::class,
        \Illuminate\Routing\Middleware\SubstituteBindings::class,
    ]);
})

Laravel 10:

Add the middleware to the web middleware group in app/Http/Kernel.php.

// app/Http/Kernel.php
protected $middlewareGroups = [
    'web' => [
        //...
        \Illuminate\Session\Middleware\StartSession::class, // <= after this
        //...
        \CodeZero\Localizer\Middleware\SetLocale::class,
        \Illuminate\Routing\Middleware\SubstituteBindings::class, // <= before this
    ],
];

⚙ Configure

Publish Configuration File

php artisan vendor:publish --provider="CodeZero\Localizer\LocalizerServiceProvider" --tag="config"

You will now find a localizer.php file in the config folder.

Configure Supported Locales

Add any locales you wish to support to your published config/localizer.php file:

'supported_locales' => ['en', 'nl'];

By default, the UrlDetector will look for these locales in the URL.

You can also use one or more custom slugs for a locale:

'supported_locales' => [
    'en' => 'english-slug',
    'nl' => ['dutch-slug', 'nederlandse-slug'],
];

Or you can use one or more custom domains for a locale:

'supported_locales' => [
    'en' => 'english-domain.test',
    'nl' => ['dutch-domain.test', 'nederlands-domain.test'],
];

🔍 Detectors

By default, the middleware will use the following detectors to check for a supported locale in:

Update the detectors array in the config file to choose which detectors to run and in what order.

You can create your own detector by implementing the CodeZero\Localizer\Detectors\Detector interface and add a reference to it in the config file. The detectors are resolved from Laravel's IOC container, so you can add any dependencies to your constructor.

💾 Stores

The first supported locale that is returned by a detector will automatically be stored in:

Update the stores array in the config file to choose which stores to use.

You can create your own store by implementing the CodeZero\Localizer\Stores\Store interface and add a reference to it in the config file. The stores are resolved from Laravel's IOC container, so you can add any dependencies to your constructor.

🛠 More Configuration

☑ omitted_locale

If you don't want your main locale to have a slug, you can set it as the omitted_locale (not the custom slug).

If you do this, no additional detectors will run after the UrlDetector and OmittedLocaleDetector. This makes sense, because the locale will always be determined by those two in this scenario.

Example:

'omitted_locale' => 'en',

Result:

• /example-route (English without slug)
• /nl/example-route (Other locales with slug)

Default: null

☑ trusted_detectors

Add any detector class name to this array to make it trusted. (do not remove it from the detectors array) When a trusted detector returns a locale, it will be used as the app locale, regardless if it's a supported locale or not.

Default: []

☑ url_segment

The index of the URL segment that has the locale, when using the UrlDetector.

Default: 1

☑ route_action

The custom route action that holds the locale, when using the RouteActionDetector.

Default: locale

To use the custom route action locale, you register a route like this:

Route::group(['locale' => 'nl'], function () {
    //Route::get(...);
});

☑ user_attribute

The attribute on the user model that holds the locale, when using the UserDetector. If the user model does not have this attribute, this detector check will be skipped.

Default: locale

☑ session_key

The session key that holds the locale, when using the SessionDetector and SessionStore.

Default: locale

☑ cookie_name

The name of the cookie that holds the locale, when using the CookieDetector and CookieStore.

Default: locale

☑ cookie_minutes

The lifetime of the cookie that holds the locale, when using the CookieStore.

Default: 60 * 24 * 365 (1 year)

🚧 Testing

composer test

☕ Credits

• Ivan Vermeyen
• All contributors

🔒 Security

If you discover any security related issues, please e-mail me instead of using the issue tracker.

📑 Changelog

A complete list of all notable changes to this package can be found on the releases page.

📜 License

The MIT License (MIT). Please see License File for more information.