Weave Code
Translation Bundle Laravel Package
enhavo/translation-bundle
Enhavo Translation Bundle is a subtree split of the open-source Enhavo CMS, a flexible PHP CMS built on the full-stack Symfony framework for managing complex data structures through a clean, usable interface.
[READ-ONLY] EnhavoTranslationBundle
Frequently asked questions about Translation Bundle
- Is enhavo/translation-bundle a Laravel package?
- No. It is a Symfony bundle and a read-only subtree split of the Enhavo CMS monorepo, with no Laravel service provider, no publishable config, no Eloquent trait, and no Blade or Livewire surface. It only makes sense inside the Enhavo distribution, so there is no drop-in path into a Laravel application.
- Can I install enhavo/translation-bundle in a Laravel app with Composer?
- Composer may resolve the package, but nothing will wire up: there is no Laravel integration layer, no config publishing, and no migration or routing hooks. Requiring the split directly alongside its parent also risks duplicate autoloading and class collisions. For Laravel multilingual content, use spatie/laravel-translatable or astrotomic/laravel-translatable instead.
- How do I install EnhavoTranslationBundle?
- The split repository documents no installation steps; its README is branding plus a redirect to the main enhavo/enhavo repository. The only supported path is to require the full Enhavo distribution or the Enhavo skeleton and enable the translation bundle through standard Symfony bundle registration. The split exists as a browsable mirror, not as an independently installable package.
- What Laravel package should I use instead for translatable Eloquent models?
- For Laravel, spatie/laravel-translatable and astrotomic/laravel-translatable both provide per-attribute model translations with published configuration, migration guidance, and a large body of community answers. Neither of those things exists for the Enhavo split. Treat the substitution as a short decision rather than a migration project.
- Which PHP and Symfony versions does enhavo/translation-bundle require?
- The split does not publish a version matrix, and the real constraints live in the parent enhavo/enhavo composer.json and its tagged releases. Check those against your PHP and Symfony LTS targets before scheduling any work. Because the split tags are generated automatically, they can drift from the parent's tagged releases.
- Why is enhavo/translation-bundle marked READ-ONLY?
- It is an automated subtree split of the Enhavo CMS monorepo, so commits, issues, and pull requests belong upstream in enhavo/enhavo. Fixes and security patches land there and propagate to the split on the next split run. That also means the mirror can lag behind upstream, and pinning the split independently is a reproducibility hazard.
- Should I add enhavo/translation-bundle as a dependency alongside enhavo/enhavo?
- No. Requiring the split directly next to the parent distribution risks double autoloading and class collisions. Enforce the rule with a Composer conflict entry or a CI check that fails when the split appears in the lock file. The full distribution is the only supported consumption path.
- Is enhavo/translation-bundle production ready and actively maintained?
- The split shows no independent adoption signal: zero stars, zero dependents, and a readme-only maturity indicator. That is not evidence of poor code, but it means no third-party examples, no Stack Overflow corpus, and a thin hiring pool. Judge maintenance cadence, commit frequency, and bus factor on the parent enhavo/enhavo repository instead.
- Does the translation bundle own the database schema and migrations for translated content?
- That is unclear from the split alone; translation storage is likely defined in the parent's resource and entity layer rather than in this bundle. Schema ownership determines the migration blast radius if you adopt Enhavo. Confirm it by reading the parent composer.json and service definitions before committing to anything.
- Can I use only the translation parts of Enhavo in my own Symfony project?
- The bundle's value is tied to Enhavo's admin UI, resource layer, and entity conventions, so partial adoption is poor if you are on Symfony without Enhavo. If you only want the translation domain model, fork and vendor the relevant classes under your own namespace. That decouples you from split drift at the cost of losing upstream fixes.
Weaver
How can I help you explore Laravel packages today?