Weave Code
Translation Bundle Laravel Package
openclassrooms/translation-bundle
Symfony bundle for managing translations with a database-backed workflow. It provides Doctrine storage and Symfony translator integration so multilingual content can be maintained without editing source files—useful for teams running multi-locale PHP applications.
Symfony2 Bundle for Translation Workflow
Frequently asked questions about Translation Bundle
- Is openclassrooms/translation-bundle a Laravel package?
- No. It is a Symfony2 bundle for managing translations with a database-backed workflow, built around Symfony's kernel, service container, configuration model and event dispatcher. Laravel uses a different container, lifecycle and translation conventions, so the bundle is not a Laravel package and cannot be dropped into a Laravel application.
- Can I install openclassrooms/translation-bundle in a Laravel app with Composer?
- Composer may resolve and install it in some setups, but installing it does not make it work. The bundle expects Symfony2 bundle registration, Doctrine wiring and Symfony console commands, and Laravel's package discovery and service providers do not understand Symfony bundles. Expect container boot failures, autoload collisions or dependency conflicts with modern PHP and Laravel versions.
- What does openclassrooms/translation-bundle actually do?
- It provides a Symfony bundle for a translation workflow, storing translations through Doctrine and integrating with the Symfony translator so multilingual content can be edited without touching source files. The intent is to let teams maintain translations in a database rather than only in YAML, XLIFF or PHP files. It is a workflow and storage layer, not a machine translation service.
- Which Laravel versions does this package support?
- None. The bundle targets Symfony2, which is end-of-life, and its PHP version constraints are likely incompatible with modern Laravel releases. There is no Laravel service provider, facade or config file, so there is no supported Laravel version to point to.
- How do you install openclassrooms/translation-bundle?
- In a Symfony2 application you would require it via Composer, register the bundle in AppKernel, configure Doctrine storage and adjust Symfony translator settings. That flow has no equivalent in Laravel, where you would register a service provider and publish config instead. Because the bundle predates modern Symfony, dependency pinning is usually required even in Symfony projects.
- What is a good Laravel alternative for database-backed translations?
- Use a Laravel-native loader such as spatie/laravel-translation-loader, which stores translations in a database table and plugs into Laravel's translator, or write a custom translation loader if your schema is unusual. Pair that with Laravel's __() helper, caching and queued import/export jobs for the workflow. This keeps everything inside Laravel's container, Eloquent and testing tools.
- Is openclassrooms/translation-bundle maintained and safe for production?
- Treat it as high risk. It targets an end-of-life Symfony2, has no stars and no dependents, and shows little ecosystem validation or upstream activity. Adopting it means owning forks, dependency pinning and security review yourself, which is rarely worth it for a Laravel product.
- How do I migrate from this bundle to a Laravel implementation?
- Do not plan a direct migration, because the runtime wiring is Symfony-specific. Instead, run a short discovery to capture workflow states, roles, translation storage format, import/export needs and approval rules, then reimplement those concepts natively with Laravel's translation loader, database or JSON storage, events, policies and an admin UI. The bundle is useful as a requirements reference, not as infrastructure.
- Does it integrate with Laravel's translator or the __() helper?
- No. The bundle hooks into Symfony's translator and Doctrine, not Laravel's translator contract or file-based lang directory conventions. Laravel's __() helper resolves through its own loader and locale handling, so translations stored by this bundle would not be discovered. Any bridge would be bespoke and fragile.
- How should I test a translation workflow in a Laravel application?
- Write feature tests that assert translations resolve for each supported locale, that missing keys fall back correctly and that admin edits persist and clear caches. Add CI checks that compare translation keys across locales to catch gaps before deployment. If you use import/export, test those as queued jobs with mocked failures so partial writes are caught.
Weaver
How can I help you explore Laravel packages today?