Easy i18n localization for Laravel, an useful tool to combine with Laravel localization classes.
The package offers the following:
Laravel | laravel-localization |
---|---|
4.0.x | 0.13.x |
4.1.x | 0.13.x |
4.2.x | 0.15.x |
5.0.x/5.1.x | 1.0.x |
5.2.x-5.4.x (PHP 7 not required) | 1.2.x |
5.2.x-5.8.x (PHP 7 required) | 1.3.x |
5.2.0-6.x (PHP 7 required) | 1.4.x |
5.2.0-8.x (PHP 7 required) | 1.6.x |
Install the package via composer: composer require mcamara/laravel-localization
For Laravel 5.4 and below it necessary to register the service provider.
In order to edit the default configuration you may execute:
php artisan vendor:publish --provider="Mcamara\LaravelLocalization\LaravelLocalizationServiceProvider"
After that, config/laravellocalization.php
will be created.
The configuration options are:
You may register the package middleware in the app/Http/Kernel.php
file:
<?php namespace App\Http;
use Illuminate\Foundation\Http\Kernel as HttpKernel;
class Kernel extends HttpKernel {
/**
* The application's route middleware.
*
* @var array
*/
protected $routeMiddleware = [
/**** OTHER MIDDLEWARE ****/
'localize' => \Mcamara\LaravelLocalization\Middleware\LaravelLocalizationRoutes::class,
'localizationRedirect' => \Mcamara\LaravelLocalization\Middleware\LaravelLocalizationRedirectFilter::class,
'localeSessionRedirect' => \Mcamara\LaravelLocalization\Middleware\LocaleSessionRedirect::class,
'localeCookieRedirect' => \Mcamara\LaravelLocalization\Middleware\LocaleCookieRedirect::class,
'localeViewPath' => \Mcamara\LaravelLocalization\Middleware\LaravelLocalizationViewPath::class
];
}
Add the following to your routes file:
// routes/web.php
Route::group(['prefix' => LaravelLocalization::setLocale()], function()
{
/** ADD ALL LOCALIZED ROUTES INSIDE THIS GROUP **/
Route::get('/', function()
{
return View::make('hello');
});
Route::get('test',function(){
return View::make('test');
});
});
/** OTHER PAGES THAT SHOULD NOT BE LOCALIZED **/
Once this route group is added to the routes file, a user can access all locales added into supportedLocales
(en
and es
by default).For example, the above route file creates the following addresses:
// Set application language to English
http://url-to-laravel/en
http://url-to-laravel/en/test
// Set application language to Spanish
http://url-to-laravel/es
http://url-to-laravel/es/test
// Set application language to English or Spanish (depending on browsers default locales)
// if nothing found set to default locale
http://url-to-laravel
http://url-to-laravel/test
The package sets your application locale App::getLocale()
according to your url. The locale may then be used for Laravel's localization features.
You may add middleware to your group like this:
Route::group(
[
'prefix' => LaravelLocalization::setLocale(),
'middleware' => [ 'localeSessionRedirect', 'localizationRedirect', 'localeViewPath' ]
], function(){ //...
});
1.: It is strongly recommended to use a redirecting middleware.Urls without locale should only be used to determine browser/default locale and to redirect to the localized url.Otherwise, when search engine robots crawl for example http://url-to-laravel/test
they may get different language content for each visit.Also having multiple urls for the same content creates a SEO duplicate-content issue.
2.: It is strongly recommended to localize your links, even if you use a redirect middleware.Otherwise, you will cause at least one redirect each time a user clicks on a link.Also, any action url from a post form must be localized, to prevent that it gets redirected to a get request.
The following redirection middleware depends on the settings of hideDefaultLocaleInURL
and useAcceptLanguageHeader
in config/laravellocalization.php
:
Whenever a locale is present in the url, it will be stored in the session by this middleware.
In there is no locale present in the url, then this middleware will check the following
useAcceptLanguageHeader
is set to true, compute locale from browser and redirect to url with locale.hideDefaultLocaleInURL
is set to true.For example, if a user navigates to http://url-to-laravel/test and en
is the current locale, it would redirect him automatically to http://url-to-laravel/en/test.
Similar to LocaleSessionRedirect, but it stores value in a cookie instead of a session.
Whenever a locale is present in the url, it will be stored in the cookie by this middleware.
In there is no locale present in the url, then this middleware will check the following
useAcceptLanguageHeader
is set to true, compute locale from browser and redirect to url with locale.hideDefaultLocaleInURL
is set to true.For example, if a user navigates to http://url-to-laravel/test and de
is the current locale, it would redirect him automatically to http://url-to-laravel/de/test.
When the default locale is present in the url and hideDefaultLocaleInURL
is set to true, then the middleware redirects to the url without locale.
For example, if es
is the default locale, then http://url-to-laravel/es/test would be redirected to http://url-to-laravel/test and theApp::getLocale()
would beset to es
.
This package comes with a bunch of helpers.
Localized URLS taken into account route model binding when generating the localized route,aswell as the hideDefaultLocaleInURL
and Translated Routes settings.
// If current locale is Spanish, it returns `/es/test`
<a href="{{ LaravelLocalization::localizeUrl('/test') }}">@lang('Follow this link')</a>
Get current URL in specific locale:
// Returns current url with English locale.
{{ LaravelLocalization::getLocalizedURL('en') }}
Returns a URL clean of any localization.
// Returns /about
{{ LaravelLocalization::getNonLocalizedURL('/es/about') }}
Returns a route, localized to the desired locale. If the translation key does not exist in the locale given, this function will return false.
// Returns /es/acerca
{{ LaravelLocalization::getURLFromRouteNameTranslated('es', 'routes.about') }}
Return all supported locales and their properties as an array.
{{ LaravelLocalization::getSupportedLocales() }}
Return all supported locales but in the order specified in the configuration file. You can use this function to print locales in the language selector.
{{ LaravelLocalization::getLocalesOrder() }}
Return an array with all the keys for the supported locales.
{{ LaravelLocalization::getSupportedLanguagesKeys() }}
Return the key of the current locale.
{{ LaravelLocalization::getCurrentLocale() }}
Return current locale's name as string (English/Spanish/Arabic/ ..etc).
{{ LaravelLocalization::getCurrentLocaleName() }}
Return current locale's native name as string (English/Español/عربى/ ..etc).
{{ LaravelLocalization::getCurrentLocaleNative() }}
Return current locale's direction as string (ltr/rtl).
{{ LaravelLocalization::getCurrentLocaleDirection() }}
Return the ISO 15924 code for the current locale script as a string; "Latn", "Cyrl", "Arab", etc.
{{ LaravelLocalization::getCurrentLocaleScript() }}
Register the middleware LaravelLocalizationViewPath
to set current locale as view-base-path.
Now you can wrap your views in language-based folders like the translation files.
resources/views/en/
, resources/views/fr
, ...
As you can modify the supportedLocales even by renaming their keys, it is possible to use the string uk
instead of en-GB
to provide custom lang url segments. Of course, you need to prevent any collisions with already existing keys and should stick to the convention as long as possible. But if you are using such a custom key, you have to store your mapping to the localesMapping
array. This localesMapping
is needed to enable the LanguageNegotiator to correctly assign the desired locales based on HTTP Accept Language Header. Here is a quick example how to map HTTP Accept Language Header 'en-GB' to url segment 'uk':
// config/laravellocalization.php
'localesMapping' => [
'en-GB' => 'uk'
],
After that http://url-to-laravel/en-GB/a/b/c
becomes http://url-to-laravel/uk/a/b/c
.
LaravelLocalization::getLocalizedURL('en-GB', 'a/b/c'); // http://url-to-laravel/uk/a/b/c
LaravelLocalization::getLocalizedURL('uk', 'a/b/c'); // http://url-to-laravel/uk/a/b/c
If you're supporting multiple locales in your project you will probably want to provide the users with a way to change language. Below is a simple example of blade template code you can use to create your own language selector.
<ul>
@foreach(LaravelLocalization::getSupportedLocales() as $localeCode => $properties)
<li>
<a rel="alternate" hreflang="{{ $localeCode }}" href="{{ LaravelLocalization::getLocalizedURL($localeCode, null, [], true) }}">
{{ $properties['native'] }}
</a>
</li>
@endforeach
</ul>
Here default language will be forced in getLocalizedURL() to be present in the URL even hideDefaultLocaleInURL = true
.
Note that Route Model Binding is supported.
You may translate your routes. For example, http://url/en/about and http://url/es/acerca (acerca is about in spanish)or http://url/en/article/important-article and http://url/es/articulo/important-article (article is articulo in spanish) would be redirected to the same controller/view as follows:
It is necessary that at least the localize
middleware in loaded in your Route::group
middleware (See installation instruction).
For each language, add a routes.php
into resources/lang/**/routes.php
folder.The file contains an array with all translatable routes. For example, like this:
<?php
// resources/lang/en/routes.php
return [
"about" => "about",
"article" => "article/{article}",
];
<?php
// resources/lang/es/routes.php
return [
"about" => "acerca",
"article" => "articulo/{article}",
];
You may add the routes in routes/web.php
like this:
Route::group(['prefix' => LaravelLocalization::setLocale(),
'middleware' => [ 'localize' ]], function () {
Route::get(LaravelLocalization::transRoute('routes.about'), function () {
return view('about');
});
Route::get(LaravelLocalization::transRoute('routes.article'), function (\App\Article $article) {
return $article;
});
//,...
});
Once files are saved, you can access http://url/en/about , http://url/es/acerca , http://url/en/article/important-article and http://url/es/articulo/important-article without any problem.
Maybe you noticed in the previous example the English slug in the Spanish url:
http://url/es/articulo/important-article
It is possible to have translated slugs, for example like this:
http://url/en/article/important-change
http://url/es/articulo/cambio-importante
However, in order to do this, each article must have many slugs (one for each locale).Its up to you how you want to implement this relation. The only requirement for translatable route parameters is, that the relevant model implements the interface LocalizedUrlRoutable
.
To implement \Mcamara\LaravelLocalization\Interfaces\LocalizedUrlRoutable
,one has to create the function getLocalizedRouteKey($locale)
, which must return for a given locale the translated slug. In the above example, inside the model article, getLocalizedRouteKey('en')
should return important-change
and getLocalizedRouteKey('es')
should return cambio-importante
.
To use route-model-binding, one should overwrite the function resolveRouteBinding($slug)
in the model. The function should return the model that belongs to the translated slug $slug
.For example:
public function resolveRouteBinding($slug)
{
return static::findByLocalizedSlug($slug)->first() ?? abort(404);
}
You may want to checkout this video which demonstrates how one may set up translatable route parameters.
You can capture the URL parameters during translation if you wish to translate them too. To do so, just create an event listener for the routes.translation
event like so:
Event::listen('routes.translation', function($locale, $attributes)
{
// Do your magic
return $attributes;
});
Be sure to pass the locale and the attributes as parameters to the closure. You may also use Event Subscribers, see: http://laravel.com/docs/events#event-subscribers
To cache your routes, use:
php artisan route:trans:cache
... instead of the normal route:cache
command. Using artisan route:cache
will not work correctly!
For the route caching solution to work, it is required to make a minor adjustment to your application route provision.
In your App's RouteServiceProvider
, use the LoadsTranslatedCachedRoutes
trait:
<?php
class RouteServiceProvider extends ServiceProvider
{
use \Mcamara\LaravelLocalization\Traits\LoadsTranslatedCachedRoutes;
For more details see here.
This may happen if you do not localize your action route that is inside your Routes::group
.This may cause a redirect, which then changes the post request into a get request.To prevent that, simply use the localize helper.
For example, if you use Auth::routes()
and put them into your Route::group
Then
<form action="/logout" method="POST">
<button>Logout</button>
</form>
will not work. Instead, one has to use
<form action="{{ \LaravelLocalization::localizeURL('/logout') }} " method="POST">
<button>Logout</button>
</form>
If you do not localize your post url and use a redirect middleware,then the post request gets redirected as a get request.If you have not defined such a get route, you will cause this exception.
To localize your post url see the example in POST is not working.
This also happens if you did not localize your post url.If you don't localize your post url, the default locale is set while validating,and when returning to back()
it shows the validation message in default locale.
To localize your post url see the example in POST is not working.
During the test setup, the called route is not yet known. This means no language can be set.When a request is made during a test, this results in a 404 - without the prefix set the localized route does not seem to exist.
To fix this, you can use this function to manually set the language prefix:
// TestCase.php
protected function refreshApplicationWithLocale($locale)
{
self::tearDown();
putenv(LaravelLocalization::ENV_ROUTE_KEY . '=' . $locale);
self::setUp();
}
protected function tearDown()
{
putenv(LaravelLocalization::ENV_ROUTE_KEY);
parent::tearDown();
}
// YourTest.php
public function testBasicTest()
{
$this->refreshApplicationWithLocale('en');
// Testing code
}
Ask mcamara if you want to be one of them!
View changelog here -> changelog
Laravel Localization is an open-sourced laravel package licensed under the MIT license
项目下输入: composer require mcamara/laravel-localization 在 config/app.php 'providers' => [ // [...] Mcamara\LaravelLocalization\LaravelLocalizationServiceProvider::class, ], 'aliases' => [ // [...] 'Larav
Laravel 是一套简洁、优雅的PHP Web开发框架(PHP Web Framework)。它可以让你从面条一样杂乱的代码中解脱出来;它可以帮你构建一个完美的网络APP,而且每行代码都可以简洁、富于表达力。 功能特点 1、语法更富有表现力 你知道下面这行代码里 “true” 代表什么意思么? $uri = Uri::create(‘some/uri’, array(), array(), tr
我需要空间/Laravel权限的帮助。当我试图分配它给我错误哎呀,看起来像出了问题。 错误 Connection.php第761行中的QueryExcema:SQLSTATE[23000]:完整性约束冲突:1048列role_id不能为空(SQL:插入到(,)值(9,))
Laravel 作为现在最流行的 PHP 框架,其中的知识较多,所以单独拿出来写一篇。 简述 Laravel 的生命周期 Laravel 采用了单一入口模式,应用的所有请求入口都是 public/index.php 文件。 注册类文件自动加载器 : Laravel通过 composer 进行依赖管理,无需开发者手动导入各种类文件,而由自动加载器自行导入。 创建服务容器:从 bootstrap/ap
简介 Laravel Scout 为 Eloquent 模型 全文搜索提供了简单的,基于驱动的解决方案。通过使用模型观察者,Scout 会自动同步 Eloquent 记录的搜索索引。 目前,Scout 自带一个 Algolia 驱动;不过,编写自定义驱动很简单, 你可以轻松的通过自己的搜索实现来扩展 Scout。 安装 首先,通过 Composer 包管理器来安装 Scout: composer
简介 Laravel 致力于让整个 PHP 开发体验变得愉快, 包括你的本地开发环境。 Vagrant 提供了一种简单,优雅的方式来管理和配置虚拟机。 Laravel Homestead 是一个官方预封装的 Vagrant box,它为你提供了一个完美的开发环境,而无需在本地机器安装 PHP 、Web 服务器和其他服务器软件。不用担心会搞乱你的操作系统!Vagrant boxes 是一次性的。如果
WebStack-Laravel 一个开源的网址导航网站项目,具备完整的前后台,您可以拿来制作自己的网址导航。 部署 克隆代码: git clone https://github.com/hui-ho/WebStack-Laravel.git 安装依赖: composer installphp artisan key:generate 编辑配置: cp .env.example .env ...D
百度编辑器 For Laravel 5 支持自定义路由, 默认前后台独立控制器,支持重写方法方便自己的业务逻辑处理,支持扩展图片助手(推荐使用Intervention\Image第三方包) 官网 NinJa911工作室. 疑问讨论 请在issue里new一个. 授权 此Laravel 扩展包基于MIT协议开源MIT license. 安装 1.Composer 安装 composer requir
laravel-admin是一个基于laravel的后台管理开发框架,能帮助你使用很少的时间和代码量开发出功能完备的管理后台,另外它作为一个三方包,可以和框架内其它项目并行开发,真正做到前后台开发分离。 功能: RBAC权限管理模块。 菜单管理,和权限系统结合。 模型数据表格,能快速构建数据表格,并支持多种模型关系。 模型表单以及30+种form元素组件,自动实现增、删、改功能。 支持本地和云存储