Weave Code
Laravel Translation Editor Laravel Package
exolnet/laravel-translation-editor
Web-based editor for Laravel translation files. Browse and edit language strings directly from the browser, with support for multiple locales and file groups. Manage translations without manually editing PHP or JSON files, making it easier for teams to keep localization content up to date.
Allow translations edition through the browser
Frequently asked questions about Laravel Translation Editor
- How do I install exolnet/laravel-translation-editor in a Laravel app?
- Run composer require exolnet/laravel-translation-editor:^1.13 on a Laravel 12 application running PHP 8.3 or newer. The service provider is auto-discovered, so routes, controllers, and Blade views register automatically, and you can publish the config with php artisan vendor:publish if you need to customize paths or middleware. No database migrations, queue workers, or external services are involved. Install and validate in a non-production environment before enabling it anywhere real users can reach it.
- Which Laravel and PHP versions does this translation editor support?
- Version 1.13.0 requires PHP 8.3+ and Laravel 12+. The earlier 1.12.x line supports the previous matrix that includes Laravel 11 and PHP 8.2. Because the support drop shipped in a minor version bump, a caret constraint like ^1.12 will pull in the breaking change on composer update, so pin exact versions if you have not completed the framework upgrade.
- How do I protect the translation editor routes with authentication and authorization?
- The package registers HTTP routes that write directly to language files, so apply auth and authorization middleware through the published config before exposing it. Restrict editing to trusted staff roles only, and disable the routes entirely in production if operational editing is not required. Leaving these routes open creates a remote content-tampering surface in your application.
- Can I disable the translation editor outside local and staging environments?
- Yes. Routes are registered by the package service provider and driven by publishable config, so you can gate registration on the environment, for example only enabling it when app()->environment('local') or when an explicit feature flag is set. Pair this with middleware so production deployments default to off rather than relying on someone remembering to lock it down. Document the toggle so enabling it later is a deliberate decision.
- Does it edit both PHP array files and JSON translation files across multiple locales?
- The editor provides a browser UI for browsing and editing Laravel language files, with support for multiple locales and file groups. Laravel's PHP array and JSON language files are both part of the translation system the editor targets. Run a round-trip test on your own files in staging to confirm the edits, formatting, and cache behavior match your expectations before relying on it.
- Is exolnet/laravel-translation-editor a replacement for a TMS like Lokalise or Crowdin?
- No. It is a lightweight in-app editor, not a translation management system: it has no approval workflows, audit trails, translator assignment, or review gates. It fits small teams that want translators and project managers to update copy without hand-editing PHP or JSON files, keeping strings in the repository. If you need workflow controls or an audit history, adopt a proper TMS instead.
- What happens if two people edit the same translation string at the same time?
- File-based writes are not transactional, so concurrent saves can clobber one another and the last write wins. There is no built-in locking, versioning, or conflict resolution in this package. Coordinate editing sessions or limit editor access to one person at a time, and keep translations in version control so accidental overwrites are recoverable.
- Is v1.13.0 a breaking change from v1.12 even though it is a minor version?
- In practice yes. It drops PHP 8.2 and Laravel 11 support and raises the floor to PHP 8.3+ and Laravel 12+, which is a semver violation for a minor bump. Any project on a caret constraint like ^1.12 will receive this on composer update. Pin exact versions, review changelogs before updating, and sequence the package bump after your Laravel 12 cutover rather than alongside it.
- Is this package actively maintained and safe to depend on in production?
- It is a small, conventional Laravel package with a low surface area, but the maintainer footprint is limited, so bus factor and long-term support are the dominant risks rather than code quality. Recent releases have shipped support-matrix breaking changes in minor versions, which makes release cadence and issue responsiveness part of your risk assessment. Pin versions, document a rollback path, and be prepared to fork if maintenance stalls.
- What should I verify in my application before adopting this translation editor?
- Confirm you are on Laravel 12 and PHP 8.3+ and that no other dependency pins an older PHP or Laravel version. Check that the editor's routes and views do not conflict with existing admin routes or localization middleware, and apply auth middleware before exposing anything. Then run a translation round-trip test: edit a string, save, inspect the file diff, clear caches, and confirm both the UI and the application reflect the change.
Weaver
How can I help you explore Laravel packages today?