PHPackages                             aenzenith/laravel-localizable - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Localization & i18n](/categories/localization)
4. /
5. aenzenith/laravel-localizable

ActiveLibrary[Localization & i18n](/categories/localization)

aenzenith/laravel-localizable
=============================

A package which is allow make localization in model attribute easily

1.0.0(3y ago)011MITPHP

Since Jan 15Pushed 3y ago1 watchersCompare

[ Source](https://github.com/aenzenith/laravel-localizable)[ Packagist](https://packagist.org/packages/aenzenith/laravel-localizable)[ RSS](/packages/aenzenith-laravel-localizable/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (1)DependenciesVersions (2)Used By (0)

Laravel Localizable
===================

[](#laravel-localizable)

This trait offers an efficient and user-friendly solution for localizing model fields within a Laravel application. It grants the ability to set localizable fields without adding new database fields and the capability to translate existing table fields to different languages without adding new fields. This trait streamlines the localization process for your Laravel models by simplifying the management and maintenance of localizable fields.

Installation
------------

[](#installation)

To install the package, you can use the following commands:

```
composer require aenzenith/laravel-localizable
```

After installation completed, you have to run these commands to prepare package ready to use:

```
php artisan migrate

php artisan vendor:publish --provider="Aenzenith\LaravelLocalizable\LocalizableServiceProvider"
```

With publishing, you can access the config file from `config/localizable.php`

Usage
-----

[](#usage)

### Setting the locales list

[](#setting-the-locales-list)

You can modify the locales that will be use, in the `config/localizable.php` configuration file by adding new languages in the form of language codes and language names to the locales array. For example, if you want to add Spanish and German to the list of available languages, simply you can add the following lines to your configuration file:

```
'locales' => [
    'en' => 'English',
    'fr' => 'French',
    /* */
    'es' => 'Spanish',
    'de' => 'German',
],
```

### Adding the `Localizable` trait and `$localizable` property to your model

[](#adding-the-localizable-trait-and-localizable-property-to-your-model)

```
use Aenzenith\LaravelLocalizable\Localizable;

class Content extends Model
{
    use HasFactory, Localizable;

    protected $localizable = [
        'title',
        'content',
    ];

    /* ... */
}
```

The fields added to the `$localizable` array do not need to have a corresponding field in the database table. This allows you to add localizable attributes independently of the database, giving you the flexibility to handle localization without making changes to the underlying table structure.

However, if you wish to localize existing fields in your model, the fields added to the `$localizable` array will be returned as localized when the model is retrieved, without the need for any changes to the table structure.

### Localization process

[](#localization-process)

You can use the **getLocalizables** method to get the localizable fields of the model for each locale to pass them to the front-end. For example:

```
    $localizables = Content::getLocalizables();

    //you can pass also locales list with config('localizable.locales') for language names

    return view('content.create', compact('localizables'));
```

The `localizables` variable will be added to your view data:

```
{
  "localizables": {
    "en": {
      "title": null,
      "content": null
    },
    "fr": {
      "title": null,
      "content": null
    },
    "es": {
      "title": null,
      "content": null
    },
    "de": {
      "title": null,
      "content": null
    }
  }
}
```

You can create a form with the fields you added to the `$localizable` array and pass the `localizables` variable to the form. Then you can use the `localizables` variable to create the localized fields in the form.

Here is an example of a form that uses the `localizables` variable:

```

  @csrf @foreach ($localizables as $locale => $fields)

    ({{ $locale }}) Title

    ({{ $locale }}) Content

  @endforeach

  Submit

```

In the Vue.js with Inertia.js:

```
    return Inertia::render('Content/Create', [
        'localizables' => Content::getLocalizables(),
    ]);
```

```
import { useForm } from "@inertiajs/inertia";
import { defineProps } from "vue";

const props = defineProps({
  localizables: {
    type: Object,
    required: true,
  },
});

const form = useForm({
  localizations: props.localizables,
});

const submit = () => {
  form.post(route("content.store"));
};
```

```

        ({{ $locale }}) Title

        ({{ $locale }}) Content

    Submit

```

While utilizing the `localizables` variable to create localized fields in the form is an option, it is not a requirement. You have the freedom to use your preferred front-end framework to design these fields in a way that aligns with your project's specific needs and requirements. You only need to ensure that you pass the correct parameters to the methods used when saving to the back-end. Below you can find information about the controller methods.

When saving a model in a controller, you can use the following localization methods to handle the localization data:

1. The **localize** method allows you to localize a specific field of the model to a specific locale. It accepts three arguments: `locale`, `field` and `value`. For example:

```
    $content = new Content();
    $content->save();

    $content->localize('en', 'title', 'English Title');
    $content->localize('en', 'content', 'English Content');

    $content->localize('fr', 'title', 'French Title');
    $content->localize('fr', 'content', 'French Content');
```

2. The **localizeMany** method allows you to localize multiple fields of the model to a specific locale. It accepts two arguments: the `locale` and `an associative array of fields and their values`. For example:

```
    $content->localizeMany(
        'en',
        [
            'title' => 'English Title',
            'content' => 'English Content'
        ]
    );

    $content->localizeMany(
        'fr',
        [
            'title' => 'French Title',
            'content' => 'French Content'
        ]
    );
```

3. The **localizeManyLocales** method allows you to localize the model to multiple locales. It accepts an array where the keys are the locales and the values are arrays of fields and their values. For example:

```
    $content->localizeManyLocales(
        [
            'en' => [
                'title' => 'English Title',
                'content' => 'English Content'
            ],
            'fr' => [
                'title' => 'French Title',
                'content' => 'French Content'
            ]
        ]
    );
```

If you got the localizables with **getLocalizables** method and processed in the front-end, you can use the **localizeManyLocales** method to create the localized values easily. For example:

```
    $content->localizeManyLocales($request->localizations);
```

### Retrieving localizations for update

[](#retrieving-localizations-for-update)

You can get the localized datas with using **getLocalizations** method after you called the model.

```
    $content = Content::first()->getLocalizations();
    /* or */
    $content = Content::first();
    $content->getLocalizations();
```

The `localizations` attribute will be added to your model data:

```
{
  "localizations": {
    "en": {
      "title": "Englist Title",
      "content": "English Content"
    },
    "fr": {
      "title": "French Title",
      "content": "French Content"
    },
    "es": {
      "title": null,
      "content": null
    },
    "de": {
      "title": null,
      "content": null
    }
  }
}
```

Then you can process the localized values in front-end and pass the updated values to **localizeManyLocales** method easily. For example:

```
    $content->localizeManyLocales($request->localizations);
```

### Getting localized data

[](#getting-localized-data)

The localized data will be returned automatically according to the application locale. To change the application locale, you can use the `setLocale` method.

```
    app()->setLocale('fr');
```

#### If there is no record for the field you added to `$localizable`, the `field_fallback_value` in `config/localizable.php` will be returned. If you want it to return as null, set the `field_fallback` option to `false`.

[](#if-there-is-no-record-for-the-field-you-added-to-localizable-the-field_fallback_value-in-configlocalizablephp-will-be-returned-if-you-want-it-to-return-as-null-set-the-field_fallback-option-to-false)

```
    'field_fallback' => true,

    'field_fallback_value' => 'This field is not localized yet.',
```

All of the localized data will stored in `localizations` table. When a model is deleted, the related localizations will be deleted automatically.

License
-------

[](#license)

[MIT](https://github.com/aenzenith/laravel-localizable/blob/main/LICENSE)

Support
-------

[](#support)

If you have any questions or suggestions, please feel free to contact me. You can also open an issue on GitHub.

[!["Buy Me A Coffee"](https://camo.githubusercontent.com/9f44ce2dc3b3eecdd02598900866ffc518801df1932849703dae1e5ce5031070/68747470733a2f2f7777772e6275796d6561636f666665652e636f6d2f6173736574732f696d672f637573746f6d5f696d616765732f6f72616e67655f696d672e706e67)](https://www.buymeacoffee.com/aenzenith)

###  Health Score

21

—

LowBetter than 19% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity5

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity45

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

1212d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/1a63186396392fbbf297d035d2486ac81ebf4deb24c4ae7527da3d3c2daa5519?d=identicon)[aenzenith](/maintainers/aenzenith)

---

Top Contributors

[![aenzenith](https://avatars.githubusercontent.com/u/104267365?v=4)](https://github.com/aenzenith "aenzenith (26 commits)")

---

Tags

laravellaravel-packagelocalization

### Embed Badge

![Health badge](/badges/aenzenith-laravel-localizable/health.svg)

```
[![Health](https://phpackages.com/badges/aenzenith-laravel-localizable/health.svg)](https://phpackages.com/packages/aenzenith-laravel-localizable)
```

###  Alternatives

[symfony/translation

Provides tools to internationalize your application

6.6k836.5M2.1k](/packages/symfony-translation)[nesbot/carbon

An API extension for DateTime that supports 281 different languages.

169661.4M4.8k](/packages/nesbot-carbon)[joedixon/laravel-translation

A tool for managing all of your Laravel translations

717911.4k11](/packages/joedixon-laravel-translation)[illuminate/translation

The Illuminate Translation package.

6936.4M495](/packages/illuminate-translation)[lajax/yii2-translate-manager

Translation management extension for Yii 2

227578.8k13](/packages/lajax-yii2-translate-manager)[larswiegers/laravel-translations-checker

Make sure your laravel translations are checked and are included in all languages.

256423.2k2](/packages/larswiegers-laravel-translations-checker)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)