- Is ongr/translations-bundle compatible with Laravel?
- No. It is a Symfony bundle built around Symfony DI, compiler passes, and the ONGR ElasticsearchBundle; it has no Laravel service provider, facade, or config publish path. Integrating it would require booting a partial Symfony kernel and adding Symfony as a runtime dependency, which is not recommended for a Laravel app.
- Can I install ongr/translations-bundle in a Laravel project?
- Composer may block installation on modern PHP because the package targets the Symfony 2.7/3.x and Elasticsearch 1.x/2.x era. Even if forced, you would still need a compatible ONGR ElasticsearchBundle, an EOL Elasticsearch cluster, and Symfony container semantics. There is no supported Laravel integration path.
- What Laravel versions does ongr/translations-bundle support?
- None. The package is not a Laravel package and does not declare Laravel framework support; its dependencies and architecture are Symfony-centric. Do not expect it to work with Laravel 8, 9, 10, or 11 without a rewrite.
- What is ongr/translations-bundle used for?
- It is a Symfony bundle that provides a translations GUI and stores localized translation documents in Elasticsearch via the ONGR ElasticsearchBundle. It is intended for translating Symfony static strings and querying multilingual content from Elasticsearch. It is not a general-purpose Laravel translation loader.
- Does ongr/translations-bundle support PHP 8?
- No. The last release was in 2016 and the dependency set is pinned to the Symfony 2.7/3.x and Elasticsearch 1.x/2.x era, so PHP 8 compatibility is not expected. Composer resolution will likely fail or require aggressive dependency overrides. There is no maintained security or compatibility patch path.
- What Elasticsearch version does ongr/translations-bundle require?
- It depends on the ONGR ElasticsearchBundle and elasticsearch-php client from the ES 1.x/2.x era. That means you need an Elasticsearch 1.x or 2.x cluster, which is long past end-of-life and generally unavailable on managed cloud services. Modern Elasticsearch 7.x/8.x clusters are not supported without porting the client usage.
- Is ongr/translations-bundle maintained?
- No. The last release was 2016-07-27, the repository has very few stars and zero dependents, and there is no recent commit activity. There is no evidence of maintainer responsiveness, security patching, or a community to rely on for workarounds. Treat it as abandoned for new development.
- What are good Laravel alternatives to ongr/translations-bundle?
- For database-backed translations, use spatie/laravel-translation-loader; for translated Eloquent attributes, use astrotomic/laravel-translatable; for locale routing and negotiation, use mcamara/laravel-localization. Laravel's built-in translator, based on symfony/translation, already covers fallback chains and per-locale retrieval. If you truly need searchable multilingual documents, use the modern elasticsearch/elasticsearch client directly.
- How do I migrate from ongr/translations-bundle to Laravel?
- Treat it as a data extraction, not a code port. Export the translation documents from Elasticsearch to JSON or a relational table, normalize locale and document-type keys, and load them into a maintained Laravel translation store. Run a parallel window with the old index read-only and diff rendered output per locale before cutover.
- Can I use ongr/translations-bundle for multilingual Eloquent models?
- No. It is not designed for Eloquent models or Laravel's database layer; it stores and queries translation documents through ONGR Elasticsearch services. For translated model attributes in Laravel, use a package such as astrotomic/laravel-translatable or spatie/laravel-translatable. Keep Elasticsearch out of the model translation path unless search is a hard requirement.