Weave Code
Settings Bundle Laravel Package
sylius/settings-bundle
Sylius Settings Bundle adds a database-backed settings system to Sylius apps, letting admins edit runtime configuration in the admin panel and developers read values via a simple service or Twig helpers. Grouped settings are persisted, so store configuration changes without code deployments.
[READ-ONLY] Flexible settings system (with web UI) for Symfony2 applications.
Frequently asked questions about Settings Bundle
- Can I use sylius/settings-bundle in a Laravel application?
- No, not directly. It is a Symfony2 bundle that depends on AppKernel bundle registration, Symfony DI service definitions, Doctrine ORM mappings, Twig templates, Symfony Form types, and Symfony routing. Laravel exposes none of those extension points, and there is no adapter, service-provider shim, or bridge that makes the bundle run under Laravel. Direct installation should not be attempted.
- Is sylius/settings-bundle compatible with Laravel 10 or Laravel 11?
- No. It is built for the Symfony 2 full-stack framework, not Laravel. Symfony 2 reached end of life in November 2018, so the dependency tree will not install cleanly on PHP 8.x without patching, and Laravel 10 and 11 require modern PHP versions. The version constraints and framework contracts are incompatible.
- What is the best Laravel alternative to Sylius Settings Bundle?
- spatie/laravel-settings is the default recommendation. It provides typed settings classes, per-model scoping, and cache integration, and it is actively maintained. It covers most of the bundle's domain model, including typed key/value settings, namespaces, and runtime resolution, without Symfony coupling. Choose something else only if you need a specific Sylius behaviour.
- How do I install sylius/settings-bundle in Laravel with Composer?
- You should not. Composer may resolve the package, but the bundle will not boot in Laravel because it expects Symfony bundle registration, container services, Doctrine mappings, and Twig. There is no Laravel service provider, facade, or config file. Use a Laravel-native settings package instead.
- Does sylius/settings-bundle work on PHP 8?
- Not cleanly. The bundle targets Symfony 2, which is end of life, and its pinned transitive Symfony components carry unpatched advisories. Installing on PHP 8.x typically requires patching constraints and code, and you would own those patches indefinitely. That makes it unsuitable for new Laravel projects.
- Is sylius/settings-bundle still maintained?
- No. The repository is archived and read-only, with no security patches, no PHP compatibility fixes, and no issue triage. It has roughly 21 stars and zero dependents, so there is no community lifeboat or realistic upstream support path. Any vulnerability in the bundle or its Symfony 2 dependencies becomes permanently yours.
- How do I migrate Sylius settings data to Laravel?
- Treat the bundle as a written spec rather than a runtime dependency. Export the stored settings, including name, scope or namespace, type, serialized value, and cached accessor behaviour, then create a Laravel settings table with typed Eloquent casts and a cache-aside repository. Rebuild the admin screen in Nova, Filament, or Blade. The Doctrine mappings cannot be read through Eloquent without a heavy Doctrine bridge or a data migration.
- Can I reuse the Sylius settings admin UI in Laravel Nova or Filament?
- No. The admin UI is built with Symfony Form types, Twig templates, Symfony routing, and config, which have no equivalent runtime in Laravel. You can replicate the screens and field types conceptually in Nova or Filament, but the templates and form classes are not portable. Budget for a rewrite of the UI layer.
- What features does sylius/settings-bundle provide?
- It adds a database-backed, grouped settings system with a web admin UI for Symfony2 applications. Settings are namespaced and typed, persisted through Doctrine, and read at runtime via a service or Twig helpers. That domain model, typed key/value settings with scope and caching, is reusable as a specification, but essentially none of the implementation is reusable in Laravel.
- Is sylius/settings-bundle safe to use in production?
- No, especially not in a Laravel production app. The bundle is archived, its Symfony 2 foundation is end of life, and there are no security patches or PHP 8 compatibility fixes. Technical risk is high and asymmetric: the downside is unbounded while the upside is a commodity capability already solved by maintained Laravel packages. Choose an active alternative or a small in-house build.
Weaver
How can I help you explore Laravel packages today?