vsch / laravel-translation-manager
Enhanced Laravel Translation Manager
Installs: 188 532
Dependents: 3
Suggesters: 1
Security: 0
Stars: 181
Watchers: 7
Forks: 84
Open Issues: 38
Language:JavaScript
Requires
- php: >=7.2
- doctrine/dbal: ~2.9
- illuminate/support: ^6.0
- illuminate/translation: ^6.0
- laravel/helpers: ^1.1
- laravelcollective/html: ^6.0
- symfony/finder: ~4.3
Requires (Dev)
- fzaninotto/faker: ~1.4
- mockery/mockery: 0.9.*
- phpspec/phpspec: ~5.1
- phpunit/phpunit: ~8.0
- dev-master
- 6.0.0
- 2.6.46
- 2.6.44
- 2.6.42
- 2.6.40
- 2.6.38
- 2.6.36
- 2.6.34
- 2.6.32
- 2.6.30
- 2.6.28
- 2.6.26
- 2.6.24
- 2.6.22
- 2.6.20
- 2.6.18
- 2.6.16
- 2.6.14
- 2.6.12
- 2.6.10
- 2.6.6
- 2.6.4
- 2.6.2
- 2.6.0
- 2.5.20
- 2.5.18
- 2.5.16
- 2.5.14
- 2.5.12
- 2.5.10
- 2.5.8
- 2.5.6
- 2.5.4
- 2.5.2
- 2.5.0
- 2.4.42
- 2.4.40
- 2.4.38
- 2.4.36
- 2.4.34
- 2.4.32
- 2.4.30
- 2.4.28
- 2.4.26
- 2.4.24
- 2.4.22
- 2.4.20
- 2.4.14
- 2.4.12
- 2.4.11
- 2.4.10
- 2.4.8
- 2.4.6
- 2.4.5
- 2.4.4
- 2.4.3
- 2.4.2
- 2.4.1
- 2.4.0
- 2.3.14
- 2.3.12
- 2.3.10
- 2.3.8
- 2.3.7
- 2.3.6
- 2.3.5
- 2.3.4
- 2.3.3
- 2.3.2
- 2.3.1
- 2.1.4
- 2.1.3
- 2.1.2
- 2.1.1
- 2.1.0
- 2.0.41
- 2.0.40
- 2.0.39
- 2.0.38
- 2.0.37
- 2.0.36
- 2.0.35
- 2.0.34
- 2.0.33
- 2.0.32
- 2.0.31
- 2.0.30
- 2.0.29
- 2.0.28
- 2.0.27
- 2.0.26
- 2.0.19
- 2.0.18
- 2.0.17
- 2.0.16
- 2.0.15
- 2.0.14
- 2.0.13
- 2.0.12
- 2.0.11
- 2.0.10
- 2.0.9
- 2.0.8
- 2.0.7
- 2.0.6
- 2.0.5
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- 1.0.31
- 1.0.30
- 1.0.28
- 1.0.26
- 1.0.25
- 1.0.24
- 1.0.23
- 1.0.22
- 1.0.21
- 1.0.20
- 1.0.19
- 1.0.18
- 1.0.17
- 1.0.16
- 1.0.15
- 1.0.14
- 1.0.13
- 1.0.12
- 1.0.11
- 1.0.10
- 1.0.9
- 1.0.8
- 1.0.7
- 1.0.6
- 1.0.5
- 1.0.4
- 1.0.3
- 1.0.2
- 1.0.1
- 1.0.0
- 0.2.4
- 0.2.3
- 0.2.2
- 0.2.1
- 0.2.0
- 0.1.17
- 0.1.16
- 0.1.15
- 0.1.14
- 0.1.13
- 0.1.12
- 0.1.11
- 0.1.10
- 0.1.9
- 0.1.8
- 0.1.7
- 0.1.6
- 0.1.5
- 0.1.4
- 0.1.3
- 0.1.2
- 0.1.1
- 0.1
- 0.0.39
- dev-dependabot/npm_and_yarn/axios-0.21.1
- dev-Laravel-6.0
- dev-Laravel-5.3
- dev-Laravel-5.5
- dev-Laravel-5.4
This package is auto-updated.
Last update: 2024-11-05 08:43:36 UTC
README
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
⚠️ Only MySQL and PostgreSQL Database connections are supported. Adding another database only requires additional repository interface implementations following the examples of MysqlTranslatorRepository.php or PostgresTranslatorRepository.php.
⚠️ Version 2.6.10 has a new migration
When upgrading from earlier versions run:
$ php artisan vendor:publish --provider="Vsch\TranslationManager\ManagerServiceProvider" --tag=public --force $ php artisan vendor:publish --provider="Vsch\TranslationManager\ManagerServiceProvider" --tag=migrations $ php artisan migrate
Supported Laravel Versions
For Laravel 6.0 require:
"vsch/laravel-translation-manager": "~6.0"
For Laravel 5.6 require:
"vsch/laravel-translation-manager": "~2.6"
For Laravel 5.5 require:
"vsch/laravel-translation-manager": "~2.5"
For Laravel 5.4 require:
"vsch/laravel-translation-manager": "~2.4"
For Laravel 5.3 require:
"vsch/laravel-translation-manager": "~2.3"
For Laravel 5.2 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.
Detailed information is now in the wiki.
Installation
Configuration
Version Notes
2.6.16 Adds React App UI as an alternative to WebUI
Version 2.6.10 released
React UI added as an option to WebUI.
Code updated for Laravel 5.6 compatibility
Support for JSON translation files added. Versioninfo.md
Version 2.5.6 released
Support for JSON translation files added. Versioninfo.md
Code updated for Laravel 5.5 compatibility
Version 2.4.36 released
Support for JSON translation files added. Versioninfo.md
Important LTM Translator method changes to restore compatibility with Laravel 5.4 API. These changes affect the order of arguments to the LTM Translator implementation. If you were using these methods based on previous LTM implementation then you will need to make changes in your code:
From transChoice($id, $number, array $parameters = array(), $domain = 'messages', $locale = null, $useDB = null)
to transChoice($id, $number, array $parameters = array(), $locale = null, $domain = 'messages', $useDB = null)
From trans($id, array $parameters = array(), $domain = 'messages', $locale = null, $useDB = null)
to trans($id, array $parameters = array(), $locale = null, $domain = 'messages', $useDB = null)
From get($key, array $replace = array(), $locale = null, $useDB = null)
to get($key, array $replace = array(), $locale = null, $fallback = true, $useDB = null)
Version 2.4.0 released
Laravel 5.4 compatible release. No API changes only internal implementation changes.
Version 2.3.3 released
Laravel 5.3 compatible release. For upgrade instructions see Upgrading 2.0, 2.1 to 2.3
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:
- Remove the dependency to
UserPrivilegeMapper
from your application: Removing dependency on UserPrivilegeMapper from service providers array and Removing dependency on UserPrivilegeMapper from facade alias array - Define the abilities used by LTM: Setting up user authorization
Per Locale User Access Control
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.
Screen Shot
* This package was originally based on Barry vd. Heuvel's excellent barryvdh package.