Download the PHP package brotzka/laravel-translation-manager without Composer
On this page you can find all versions of the php package brotzka/laravel-translation-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download brotzka/laravel-translation-manager
More information about brotzka/laravel-translation-manager
Files in brotzka/laravel-translation-manager
Package laravel-translation-manager
Short Description Lets you manage your Laravel-translation files via database.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-translation-manager
Laravel Translation Manager
This package provides an easy way to manage your translations in a database. It takes all files from your default locale folder (e.g. resources/lang/de) and creates translation-groups (e.g. auth.php becomes translation-group auth) which are stored in translation_groups-table. Then every entry from each file will be saved to the translations-table (yes, it takes care of multidimensional arrays of every depth).
After you have finished translating, the package writes all entries back to the resource-folder. All entries will be kept in database, so you can keep translating.
Updates are handled one-way. That means that changes which are made to a file will not replace the value in the database. The other way round, the complete content of a translation-file will be replaced by the values from the database.
Pros:
- Laravels default translation-loader will not be replaced, so everything keeps working
- Works with every Laravel version (5.*)
- To add a new language, simply add it to your
config/app.phpand re-runphp artisan translations:toDatabse, make your translations and runphp artisan translations:toFile - No more database exports! Develop locally without using the export function. Simply use your default language.
Installation
- require via composer
-
add list of available languages to your
config/app.php: - run migration
Commands
translations:toDatabase
Call via:
Collects all files and entries from within your folder and generates translations-groups and translations and writes them to the database. Existing files will NOT be updated.
translations:toFile
Call via:
Takes all entries from the database, generates missing language folders and translation-group files and puts the values to the files.
NOTE: If you want to call the commands via Artisan::call('translations.toDatabase'), you have to register both commands in app/Console/Kernel.php:
Usage
In the back, this package creates two more models (TranslationGroup and Translation) tables (translation_groups and translations).
You can use them as you are used to use models in Laravel. The relevant namespace is: Brotzka\TranslationManager\Module.
You can query relationships like this:
$translation->getParent: returns the parent-instance if existing (NULL if not)$translation->children: returns all children-instances$translation->getGroup: returns the translation-group of the current translation$translationGroup->entries: returns all entries belonging to the current translation-group
Future-Plans
- handle JSON-files
- provide some GUI-elements (e.g. language-switcher, translation-manager)
