Weave Code
Sulu Translations Bundle Laravel Package
phpro/sulu-translations-bundle
PHPro Sulu Translations Bundle adds a translations management interface to the Sulu CMS admin, letting editors view and edit Symfony translation messages per locale without touching files. It integrates with Sulu's admin UI and security, streamlining multilingual workflows.
A bundle for managing translations inside Sulu admin
Frequently asked questions about Sulu Translations Bundle
- Can I use phpro/sulu-translations-bundle in a Laravel application?
- No. Despite being listed among PHP packages, this is a Symfony bundle that extends Sulu CMS's translation infrastructure; it has no service provider, facade, or Eloquent integration and cannot be dropped into a Laravel app. For a Laravel estate, solve translation management with Laravel-native tooling such as spatie/laravel-translation-loader or astrotomic/laravel-translatable instead of bridging a Symfony bundle.
- How do I install phpro/sulu-translations-bundle?
- It is installed with Composer into an existing Sulu CMS application and enabled through the Symfony kernel, the same way other Sulu bundles are registered. It will not function outside a Symfony application running Sulu, so installation in any other framework is unsupported. Clear the cache after enabling it and confirm your Sulu core version constraints are still satisfied.
- Does version 1.2.0 really require PHP 8.4?
- Yes. The 1.2.0 release bumps the platform requirement to PHP 8.4, which is effectively a breaking change shipped in a minor version. If you are running PHP 8.1 through 8.3, pin the package to 1.1.x until your runtime is upgraded, and treat the PHP floor as a hard gate rather than a soft recommendation.
- Will the azjezz/psl to php-standard-library swap break my Composer install?
- It can. Version 1.2.0 replaces azjezz/psl with php-standard-library, which is the same library renamed upstream and therefore provides the same namespace and classes. Any other package in your dependency graph still requiring azjezz/psl will collide, so run composer why azjezz/psl before adopting. Also confirm the replacement package is available in your Composer repository or proxy.
- What can editors actually do in the Sulu admin with this bundle?
- Editors get an admin interface for managing translation messages by locale and domain, letting them view and edit Symfony translation catalogs without touching files. Access is governed by Sulu's existing permissions and configuration, so it fits into established editorial roles. Behaviour around translation handling is unchanged in 1.2.0, so regression exposure is low.
- How do I configure which locales and domains are editable?
- Catalog handling is configurable and extensible, and the bundle follows Sulu's configuration and permission conventions rather than hardcoding locales or domains. In practice you define your catalogs through the bundle's configuration in your Sulu application and the admin UI reflects that mapping. Check the bundle's configuration reference for the exact keys before wiring it into an existing project.
- Can I read or update translations from application code, not just the admin UI?
- Yes. The bundle exposes Symfony-native services for reading and updating messages, built on the Symfony Translation component, so you can use them in your own services, controllers, and console commands. This is the main developer-facing benefit over editing translation files directly. It does not provide Laravel-style facades or helpers.
- Which Sulu and Symfony versions does this bundle support?
- It targets Sulu CMS on top of Symfony and, as of 1.2.0, requires PHP 8.4 as a minimum. Before upgrading, verify that your Sulu core constraint is still satisfied alongside 1.2.0, because a bundle bump that pulls Sulu forward can cascade into a much larger CMS upgrade. Treat the runtime requirement as the deciding factor rather than the package change itself.
- Is phpro/sulu-translations-bundle actively maintained?
- It appears to be a small, narrowly scoped utility inside the larger Sulu ecosystem, and 1.2.0 is the first contribution from a new contributor. Bus factor and release cadence are the real long-term risks here, not the code change, which introduces no new features or API surface. Plan for the possibility of slow responses to issues and consider whether you can vendor or fork it if needed.
- What is the safest upgrade path from 1.1.x to 1.2.0?
- Audit your lockfile for azjezz/psl first, then upgrade the runtime to PHP 8.4 in staging. Run a full composer update on a branch, inspect the diff for the dependency swap, then run the translation-related test suite and a manual pass over the admin translation editing flows. Keep the runtime upgrade and the package bump in separate changes so you can tell which one caused a failure.
Weaver
How can I help you explore Laravel packages today?