Weave Code
Sonata Phpcr Admin Integration Bundle Laravel Package
symfony-cmf/sonata-phpcr-admin-integration-bundle
Integrates Sonata Admin with Doctrine PHPCR ODM for Symfony CMF, enabling tree-based content management and administration of hierarchical PHPCR documents through Sonata’s admin interface.
Symfony CMF sonata admin implementations
Frequently asked questions about Sonata Phpcr Admin Integration Bundle
- How do I install symfony-cmf/sonata-phpcr-admin-integration-bundle?
- Install it with Composer using composer require symfony-cmf/sonata-phpcr-admin-integration-bundle. You also need a working Symfony CMF setup with Doctrine PHPCR-ODM, Sonata Admin, and a PHPCR implementation such as Jackalope. Register the bundle in your kernel or bundles.php, then configure Sonata Admin and the PHPCR document mappings before creating admin services.
- Does this bundle work with Laravel?
- No. This is a Symfony bundle built around Symfony CMF, Sonata Admin, and Doctrine PHPCR-ODM; it does not ship a Laravel service provider, publishable config, or migrations. Evaluate it only for Symfony applications that already use PHPCR-backed content. For Laravel, you would need a different package or a custom admin layer.
- Which Symfony and Sonata Admin versions are supported?
- Compatibility is defined by the bundle's composer.json constraints, which target older Symfony and Sonata Admin generations typical of Symfony CMF. Check those constraints against your PHP, Symfony, Sonata Admin, and Doctrine PHPCR-ODM versions before requiring it. Because the project is legacy, expect to pin versions or test upgrades carefully rather than assuming current Symfony support.
- Do I need Doctrine PHPCR-ODM to use this bundle?
- Yes. The bundle is a bridge, so it assumes Doctrine PHPCR-ODM documents and a PHPCR repository are already in place. You need a PHPCR implementation such as Jackalope with Jackrabbit or doctrine-dbal, plus document mappings for the content you want to manage. Without PHPCR-ODM there is no document metadata for Sonata's admin to work with.
- How is this different from SonataDoctrinePHPCRAdminBundle?
- SonataDoctrinePHPCRAdminBundle provides Sonata Admin integration for Doctrine PHPCR-ODM itself. This CMF bundle adds the Symfony CMF layer around that integration, wiring content and routing concerns into Sonata's admin screens. Use it when you are already in Symfony CMF; for a plain PHPCR-ODM Sonata setup, the lower-level bundle may be enough.
- How do I configure Sonata Admin services for PHPCR documents?
- You register admin services for each PHPCR document class and tag them for Sonata Admin, typically with a form mapper and datagrid mapper. Configuration lives in your Symfony bundle config, where you define the admin service, document class, and tree settings. Review the bundle's documented service definitions and adapt them to your document namespaces rather than expecting Laravel-style publishable config.
- How does tree-based administration work for hierarchical PHPCR content?
- PHPCR stores content as a hierarchy, and the bundle exposes that hierarchy through Sonata Admin so editors can browse, create, move, and edit nodes in context. Tree-aware administration is the main reason to choose it over a generic CRUD screen. Performance depends on your PHPCR backend and how many child nodes are loaded per request, so test large trees in staging.
- Does it support Sonata Admin security and ACLs?
- It reuses Sonata Admin's security and ACL mechanisms, so access control is configured through Sonata roles and, where enabled, PHPCR ACLs. You should define roles per admin service and verify that tree operations such as move and delete respect those permissions. Do not assume the bundle adds authorization beyond whatSonata Admin and your PHPCR implementation enforce.
- How should I test an application that uses this bundle?
- Write functional tests that boot a Symfony kernel with a test PHPCR repository, such as Jackalope with an in-memory or disposable database, and load fixtures for the document tree. Exercise the admin routes and forms rather than only unit-testing services, because the integration is the product. Avoid running tests against production content repositories and reset state between tests.
- Is this package still maintained, and what are the alternatives?
- Treat it as a legacy Symfony CMF component: check the GitHub repository, Packagist release history, and open issues before adopting it. The 1.1.0 release has empty release notes, so review the actual diff and composer.json constraints rather than assuming the change is safe. If you need current Symfony support, budget for maintenance or consider Sulu, a custom Sonata Admin setup, or another maintained CMS layer.
Weaver
How can I help you explore Laravel packages today?