Weave Code
Backend Config Utils Bundle Laravel Package
modera/backend-config-utils-bundle
A Symfony bundle from Modera that provides utility services and helpers for backend configuration management, simplifying common configuration tasks in admin backends.
[READ-ONLY] Bundle provides tools that simplify contributing your own configuration sections to "Backend / Tools / Settings" section.
Frequently asked questions about Backend Config Utils Bundle
- Is modera/backend-config-utils-bundle compatible with Laravel?
- No. It is a Symfony bundle, not a Laravel package, and it targets Modera's own backend framework and the Backend/Tools/Settings admin surface. Laravel uses service providers, facades, and config files, while this bundle relies on Symfony bundle classes, DI extensions, compiler passes, and service tagging. Composer may install it, but Laravel package auto-discovery will not register anything and no settings screen will render.
- Can I install modera/backend-config-utils-bundle in a Laravel app with Composer?
- Composer might resolve the package in isolation, but installation does not equal integration. Expect dependency conflicts against PHP 8.2+ and Symfony 2.8/3.x-era constraints, especially because the last release was in 2016. Even a throwaway install inside a Laravel app is likely to produce constraints that cannot be satisfied without patching.
- What does modera/backend-config-utils-bundle actually do?
- It provides utility services and helpers that simplify contributing custom configuration sections to a Backend/Tools/Settings admin area. In practice, it helps declare a settings section, define fields, register it into a Modera-style admin UI, and persist values. It is plumbing for that specific Symfony backend stack, not a general Laravel settings library.
- Does modera/backend-config-utils-bundle support Laravel 10 or Laravel 11?
- No. There is no Laravel version support because the package predates and does not target Laravel's package model. It was built for Symfony bundle and dependency-injection conventions, not Laravel service providers or config/*.php. You should not expect Laravel 10 or Laravel 11 compatibility without a full native rewrite.
- What are Laravel alternatives to modera/backend-config-utils-bundle for settings management?
- Use spatie/laravel-settings for typed, grouped settings classes with migrations, or a simple Eloquent model with Cache::remember for key/value runtime settings. Static configuration belongs in config/*.php with config:cache, and admin editing can be handled by a Filament settings page, a Nova custom tool, or a simple Blade form. Validation and permissions should use Laravel Form Requests plus Gates or Policies.
- How do I reimplement the settings section concept from this bundle in Laravel?
- Start by auditing the bundle source and writing a short spec for how sections are declared, which field types exist, how values are read and written, and whether caching or permission scoping is involved. Then create one Laravel settings class per section with typed properties, defaults, and validation rules, backed by a persistence table and repository. Add cached reads, an admin page behind a Gate, and audit logging on write, then verify parity against every behavior in the spec.
- Is modera/backend-config-utils-bundle maintained and safe for production?
- No. The last release was 2016-06-10, roughly nine years ago, with zero stars and zero dependents. That means no downstream pressure to fix issues, no CVE watchers, no fork community, and no active triage. Every inherited line becomes your team's permanent maintenance burden, so this is not a safe production dependency for a Laravel application.
- Why won't Laravel package auto-discovery register modera/backend-config-utils-bundle?
- Laravel auto-discovery looks for Laravel service providers declared in Composer's extra.laravel metadata. This package is a Symfony bundle: it exposes Bundle classes, DI Extension classes, compiler passes, and service tags instead. Without a Laravel service provider and matching extra configuration, Laravel has nothing to register, so routes, views, and settings UI will not appear.
- Can I use modera/backend-config-utils-bundle with PHP 8.2 or PHP 8.3?
- Likely not without patching. The bundle dates from the PHP 5.5/7.0 era and carries Symfony 2.8/3.x constraints, so its dependency graph will probably fail to resolve on modern PHP. Before any spike, run composer why-not php 8.2 and inspect composer.json constraints to confirm the version locks. Budget for compatibility work rather than assuming a clean install.
- What is the effort to migrate from modera/backend-config-utils-bundle to a Laravel-native settings solution?
- A realistic concept transplant is about one to three days: roughly half a day to audit the bundle contract, half a day to design the settings schema, one to two days to implement persistence, cached reads, an admin page behind a Gate, and audit logging, plus half a day for parity checks. That is likely less effort than making the Symfony bundle install and run inside Laravel. Treat the repository as a design reference only and rebuild the capability natively.
Weaver
How can I help you explore Laravel packages today?