Weave Code
Acltree Bundle Laravel Package
godisco/acltree-bundle
godisco/acltree-bundle brings hierarchical ACLs to Symfony applications, letting you model resources and permissions as a tree and query access at any node through a lightweight, extensible API. Ideal for content hierarchies, nested categories, and inherited permissions.
Symfony2 Bundle for hierarchy relationship between entities with ACL Permissions.
Frequently asked questions about Acltree Bundle
- Can I use godisco/acltree-bundle in a Laravel application?
- No. godisco/acltree-bundle is a Symfony2 bundle tied to the Symfony DI container, Doctrine ORM, and the legacy symfony/security-acl component. It ships no Laravel service provider, facade, or publishable config, and Laravel's Gates and Policies use a different authorization model. Treat the repository as a design reference for inherited permissions, not a Composer dependency.
- What does godisco/acltree-bundle do?
- It models ACL permissions as a tree so child nodes inherit access rules from their parents, reducing repeated entries in complex authorization policies. It integrates with Symfony Security, stores ACL nodes and mappings through Doctrine, and supports custom permission trees. The reusable idea is pairing hierarchy traversal with an ACL resolver that walks ancestors to compute effective permissions.
- Is godisco/acltree-bundle still maintained?
- Effectively no. The bundle targets Symfony2, which reached end-of-life in November 2018, and its core dependency symfony/security-acl was deprecated in Symfony 3.0 and removed in Symfony 4.0. With 17 stars, zero dependents, and no maintainers of record, there is no upstream support or production evidence to rely on.
- How do I install godisco/acltree-bundle?
- Installation only makes sense inside a legacy Symfony2 application: add the bundle via Composer, register it in the kernel, configure Doctrine schema for ACL nodes, and enable symfony/security-acl. There is no supported Laravel installation path, and pulling it into a modern PHP 8 codebase will surface compatibility errors. For new work, use it as a reference and implement the pattern natively.
- What Laravel version is supported by godisco/acltree-bundle?
- None. The package provides no Laravel integration and was written for Symfony2, not Laravel's Gate and Policy system. Laravel version support is therefore not applicable; any Laravel implementation requires a rewrite of both persistence and authorization layers.
- How do I implement hierarchical inherited permissions in Laravel?
- Use kalnoy/nestedset for read-heavy taxonomies or staudenmeir/laravel-adjacency-list for write-heavy trees, then add spatie/laravel-permission wrapped in Gates and Policies. Resolve inherited permissions in a single service class that walks ancestors and caches effective permissions per node. Choose nested set versus adjacency list or CTE based on tree depth and how often nodes move.
- What are alternatives to godisco/acltree-bundle for Laravel?
- There is no drop-in Laravel alternative because the bundle's ACL model does not map to Laravel's authorization abstractions. Compose kalnoy/nestedset or staudenmeir/laravel-adjacency-list for hierarchy storage with spatie/laravel-permission and native Gates and Policies for authorization. The tree-traversal plus ancestor-walking resolver concept ports cleanly; the Symfony implementation does not.
- Is godisco/acltree-bundle safe for production?
- High risk. ACL inheritance is a security-critical code path where a wrong decision causes silent privilege escalation or silent lockout, and this package has zero dependents, so no production deployment has stress-tested it. It also depends on an abandoned ACL component and code from the PHP 5.x and 7.0 era that will hit PHP 8 strictness and deprecation errors. Do not deploy it as-is.
- How do I test hierarchical ACL inheritance logic?
- Write table-driven unit tests for the resolver with ancestor, descendant, sibling, and missing-node fixtures, asserting allow and deny outcomes for each inheritance case. Include tests for node moves and cache invalidation because stale permission caches are a common failure mode. In Laravel, run these with PHPUnit or Pest against a database transaction and keep the resolver framework-agnostic.
- How do I configure custom permission trees in godisco/acltree-bundle?
- In the bundle, configuration defines custom permission trees while Doctrine entities store ACL nodes and resource mappings, so inheritance is resolved from persisted data. That setup is Symfony2-specific and cannot be reused directly in Laravel. In a Laravel port, model the tree as a nested set or adjacency list table and keep permission resolution in a dedicated service behind Gates and Policies.
Weaver
How can I help you explore Laravel packages today?