- Does fsi/admin-tree-bundle work with Laravel?
- No. It is a Symfony bundle that registers through Symfony's DependencyInjection component (a Bundle subclass, an Extension, and service definitions under Resources/config) and extends FSiAdminBundle CRUD controllers. Laravel's service providers, Eloquent models, and Blade views have no corresponding integration point at any layer. Composer will download the code, but nothing in a Laravel kernel will ever boot it or route to it.
- Can I install fsi/admin-tree-bundle in a Laravel 10 or 11 app?
- Installing is technically possible but pointless. The package targets PHP 7.x and Symfony 3-4, so dependency resolution typically fails against PHP 8.1+ and modern Symfony constraints, which Laravel 10 and 11 require. Forcing it through with --ignore-platform-reqs produces a dependency tree that cannot be bootstrapped. There is no adaptation layer worth building.
- How do I add move up/down buttons to a Laravel admin list instead?
- Add an indexed integer position column to the ordered model, then expose POST /admin/{resource}/{id}/move with direction validated as up or down and wrap the swap in a transaction. Gate the route with a policy or authorization middleware and cover boundary cases such as the first item, the last item, and concurrent reorder with feature tests. If you want a package for the sortable behavior, spatie/eloquent-sortable covers a flat ordered list.
- What is the Laravel equivalent for a nested tree with reparenting?
- Use spatie/laravel-nestedset or kalnoy/nestedset rather than porting tree-move logic by hand; both handle nested set or materialized path storage with move and reparent operations. First decide whether the requirement is a flat ordered list, drag-and-drop ordering, or a genuine nested tree with depth, because those are three different data models. The choice of data model matters more than the package.
- Is fsi/admin-tree-bundle still maintained?
- No. The last release was 2020-02-17 and targets the PHP 7 / Symfony 3-4 era. Its upstream dependency, fsi/admin-bundle, is itself low activity. With 0 stars and 0 dependents there is no community triage or security review to lean on, so you would be forking and maintaining it yourself.
- Which Symfony and PHP versions does fsi/admin-tree-bundle support?
- It targets the Symfony 3-4 generation alongside PHP 7.x and depends on FSiAdminBundle as its CRUD extension point. Even inside a Symfony application it likely conflicts with Symfony 5.4, 6, or 7 constraints and PHP 8.1+. Confirm the bundle boots and the move actions render in a throwaway app matching your production version before committing to it.
- Should I use this bundle or write the tree feature natively?
- The bundle's entire surface is adding up and down actions to an admin CRUD list. In Laravel that is a route, a controller action, an integer position column, and two buttons, which is roughly a day of work with tests. Importing the dependency instead pulls a dormant Symfony, Doctrine, and Twig toolchain into a codebase that cannot execute it.
- Do the move up/down endpoints in fsi/admin-tree-bundle enforce authorization?
- The move actions are state-mutating admin endpoints, so audit whether the bundle's controllers enforce the host application's ACLs or inherit them implicitly from the surrounding admin route. If you genuinely have a Symfony host, inspect the controller code and its transaction boundaries before exposing it. In Laravel the question is moot because the bundle cannot run.
- What are the security and supply-chain risks of fsi/admin-tree-bundle?
- It is MIT licensed with a small code footprint and no obvious supply-chain concern. The real risks are framework incompatibility, which is non-recoverable without a full Symfony host app, and abandonment since 2020, which means no security review and no issue triage. Zero dependents also means no third-party usage validates it in practice.
- Should a Laravel project migrate to fsi/admin-tree-bundle?
- No, do not migrate. Treat the repository as reference material and implement native Laravel code, or adopt spatie/eloquent-sortable, spatie/laravel-nestedset, or kalnoy/nestedset depending on whether your requirement is flat ordering or a true nested tree. Only if your organization actually runs a separate Symfony service using FSiAdminBundle should you evaluate this bundle there.