Download the PHP package kenepa/translation-manager without Composer
On this page you can find all versions of the php package kenepa/translation-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download kenepa/translation-manager
More information about kenepa/translation-manager
Files in kenepa/translation-manager
Package translation-manager
Short Description Manage your application's translation strings in Filament.
License MIT
Homepage https://github.com/kenepa/translation-manager
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 translation-manager
Translation Manager
Introducing our Filament translation management tool, which allows you to easily manage, preview, and sync translations with your language files all within your Filament admin dashboard. Say goodbye to relying on developers to edit language files and streamline your localization workflow today.
Installation
You can install the package via composer:
Install via Composer.
| Plugin Version | Filament Version | PHP Version |
|---|---|---|
| <= 3.x | 2.x | > 8.0 |
| 4.x | 3.x | > 8.1 |
| 5.x | 4.x | > 8.2 |
This package uses spatie/laravel-translation-loader, publish their migration file using:
You have to update the migration file to the following:
Finally, run the migration.
Custom Theme Required
In order to compile the package views correctly, we need to create a custom Filament theme first, and then add the following path to its content. In the theme.css file of the theme, add the following line:
Register the plugin with a panel
Configuration
From version 5.x onwards, the main configuration is done through the plugin class. The traditional config file is still supported for compatibility, but all new configurations should be done through the plugin.
Plugin Configuration
Configure the plugin using fluent method chaining:
Available Configuration Methods
availableLocales(array $locales)- Set available application localesdisableKeyAndGroupEditing(bool $disable = true)- Control key/group editinglanguageSwitcher(bool $enable = true)- Enable/disable language switcherlanguageSwitcherRenderHook(string $hook)- Set render hook for language switchernavigationGroupTranslationKey(?string $key)- Set navigation group translation keynavigationGroup(?string $group)- Set navigation groupcluster(?string $cluster)- Set clusternavigationIcon(mixed $icon)- Set navigation icon (supportsfalseto disable)quickTranslateNavigationRegistration(bool $register = true)- Control quick translate navigationdontRegisterNavigationOnPanelIds(array $panelIds)- Exclude panels from navigationshowFlags(bool $show = true)- Show flags in language switcherprependDirectoryPathToGroupName(bool $prepend = true)- Control group naming
Config File
You can run the following command to publish the configuration file:
Authorization
By default, the translation manager cannot be used by anyone. You need to define the following gate in your AppServiceProvider boot method:
If you want to learn more about gates, check out the official documentation.
Legacy Configuration Examples
available_locales
Determines which locales your application supports. For example:
language_switcher
Enable or disable the language switcher feature. This allows users to switch their language - disable if you have your own implementation.
dont_register_navigation_on_panel_ids
Disable registering the translation manager navigation on certain panel IDs. The following will disable the translation navigation for the guest panel but still allow guest panel users to change the language.
Adding to cluster
Example of adding the translation manager to a cluster:
Usage
Once installed, the Translation Manager can be accessed via the Filament sidebar menu. Simply click on the "Translation Manager" link to access the translation management screen.
Upgrade Guide
Upgrading from 4.x to 5.x
Version 5.x introduces Filament v4 support and a new plugin-based configuration system. Follow these steps to upgrade:
Prerequisites
- PHP: Upgrade to PHP 8.2+
- Filament: Upgrade to Filament 4.x
Step 1: Theme Configuration (Required)
Breaking Change: Filament v4 requires a different approach for including package assets.
Remove from tailwind.config.js (if present):
Add to your custom theme CSS file:
- Create a custom theme if you don't have one (Filament v4 theme docs)
- Add this line to your theme's CSS file:
Step 2: Migrate Configuration (Recommended)
Migrate your config file settings to the plugin configuration:
License
The MIT License (MIT). Please see License File for more information.
All versions of translation-manager with dependencies
filament/filament Version ^4.0
filament/notifications Version ^4.0
spatie/laravel-package-tools Version ^1.92
spatie/laravel-translation-loader Version ^2.8
stijnvanouplines/blade-country-flags Version ^1.0.6