- Is sbs/symfony-adminlte-bundle compatible with Laravel?
- No. sbs/symfony-adminlte-bundle is a Symfony bundle, not a Laravel package: it has no Laravel service provider, package auto-discovery, Blade views, or publishable Laravel config. Running composer require in a Laravel app will not produce a working admin UI by itself. For Laravel, treat it as a reference implementation and port the Twig layouts and assets into your own Blade and Vite setup.
- Can I install sbs/symfony-adminlte-bundle with Composer in a Laravel app?
- Composer may resolve it if the declared Symfony and PHP constraints happen to match, but installation does not equal integration. You would still need to write the Laravel integration layer from scratch and adapt Twig to Blade. Because the repository is archived, dependency constraints are likely stale and may not resolve against currently supported framework versions.
- What Symfony and PHP versions does sbs/symfony-adminlte-bundle support?
- The provided overview does not state exact Symfony and PHP constraints, so check composer.json in the repository before planning any use. Because the repo is archived, those constraints are likely old and may not resolve against currently supported Symfony and PHP versions. For a legacy Symfony app, confirm the pinned Symfony and PHP pair first; for Laravel, version support is irrelevant because the bundle is not a Laravel package.
- How do I integrate AdminLTE into Laravel if this bundle is Symfony-only?
- Use the bundle only as a reference: copy Resources/views into resources/views/vendor/adminlte, convert Twig extends and block tags to Blade @extends and @section, replace Symfony path() calls with Laravel route(), and rebuild the CSS and JS through Vite. Replace the bundle's menu builder or YAML tree with a Laravel view composer or a config/adminlte.php-style array. The HTML usually transfers close to 1:1; templating, routing, and asset handling are the real work.
- Does sbs/symfony-adminlte-bundle provide Blade views or Twig templates?
- It provides Twig layouts and templates for Symfony, not Blade views. The bundle's value is its AdminLTE layout structure, sidebar and menu conventions, and asset wiring, all expressed in Twig. In Laravel you must convert those templates to Blade or copy the static AdminLTE HTML into your own views.
- Is sbs/symfony-adminlte-bundle maintained and safe for production?
- Treat it as unmaintained: the repository is archived, has very low adoption, and has no active upstream. It is not a dependency to put in a production Laravel roadmap. For a low-blast-radius internal Symfony back office, you could fork and own it, but budget for stale Composer constraints and asset updates.
- What are the best Laravel alternatives to this AdminLTE Symfony bundle?
- For Laravel admin panels, evaluate Filament, Laravel Nova, or Breeze with Livewire before porting a Symfony bundle. On Symfony, EasyAdmin is the maintained native option. If you specifically want AdminLTE's look, vendoring the static AdminLTE template and building a small Blade and Vite layout is simpler than adapting this archived bundle.
- How do I migrate off sbs/symfony-adminlte-bundle?
- Vendor the AdminLTE static assets into your own asset pipeline, copy the bundle's Resources/views into local templates, and replace bundle-provided helpers such as the menu builder and form theme with local equivalents. Do it incrementally behind an intermediate base template so application views never reference bundle paths directly. For Laravel, convert Twig to Blade, swap Symfony route helpers for Laravel route names, and use Vite instead of assets:install.
- How should I test a Laravel AdminLTE layout ported from this bundle?
- Test the rendered HTML and route and view integration rather than the original bundle: assert that layouts extend the expected base, sections render, menu items appear for the right permissions, and asset URLs resolve. Add feature tests for authenticated and unauthenticated dashboard pages, plus a smoke test that the Vite build includes AdminLTE CSS and JS. If you copied the menu builder logic, unit test the menu tree separately from the Blade rendering.
- What are the security and asset pipeline risks of the bundled AdminLTE assets?
- The bundle likely ships AdminLTE 2.x-era frontend assets tied to Bootstrap 3 and jQuery, which have browser-support and vulnerability exposure that this archived project will not patch. Confirm the actual AdminLTE, Bootstrap, and jQuery versions and verify the upstream license chain separately from the bundle's MIT license. For Laravel, rebuild assets through Vite or Encore rather than relying on Symfony assets:install symlink behavior in CI.