Package Data | |
---|---|
Maintainer Username: | duyluonglc |
Maintainer Contact: | vladimir.schneider@gmail.com (Vladimir Schneider) |
Package Create Date: | 2016-06-30 |
Package Last Update: | 2016-06-30 |
Home Page: | |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-23 03:19:14 |
Package Statistics | |
---|---|
Total Downloads: | 28 |
Monthly Downloads: | 3 |
Daily Downloads: | 0 |
Total Stars: | 1 |
Total Watchers: | 2 |
Total Forks: | 0 |
Total Open Issues: | 0 |
This package is used to comfortably manage, view, edit and translate Laravel language files with translation assistance through the Yandex Translation API. It augments the Laravel Translator system with a ton of practical functionality. Features
Detailed information is now in the wiki.
Installation
Configuration
Version Notes
- For Laravel 5.2 use the master branch, or require:
"vsch/laravel-translation-manager": "~2.1"
Laravel version 4.2 is no longer supported.
You can still get access to the last updated version. Use the
laravel4
branch, or require:"vsch/laravel-translation-manager": "~1.0"
Initial Localizations Added
If you have made correction to the auto-translated localization and would like to share them with others please do so. It will be greatly appreciated.
Now using Laravel 5 authorization API to handle all LTM related authorizations.
Find Translations now update source references for translation keys and add new keys with cleanup of dynamic keys. Need to publish and run migrations for this update Installation: Publishing And Running Migrations
Now you can view source file and line number references for translations. See Web Interface: Source References
If you are upgrading from version 2.0.x of LTM you need to:
UserPrivilegeMapper
from your application:
Removing dependency on UserPrivilegeMapper from service providers array and
Removing dependency on UserPrivilegeMapper from facade alias array
Implementation changed from the last release since using a closure in config file is not supported by the framework. Now using abilities to do the same. See Enabling per locale user access control
By default this option is turned off and any user who does not have ltm-admin-translations
ability can modify any locale. With user_locales_enabled
option enabled you can control which
locales a user is allowed to modify. Default for all users is all locales, unless you
specifically change that through the web UI, see User Admin or by populating the
ltm_user_locales
table appropriately.
* This package was originally based on Barry vd. Heuvel's excellent barryvdh package.