Weave Code
Ezobjectwrapperbundle Laravel Package
kaliop/ezobjectwrapperbundle
Kaliop eZObjectWrapperBundle provides a lightweight object wrapper for eZ Publish/Platform content in Symfony applications. It enables lazy loading and simpler access to content fields, attributes, and relations, helping developers integrate legacy eZ content into cleaner templates and controllers.
Symfony Bundle eZObjectWrapperBundle for eZPlatform and eZ Publish 5 development
Frequently asked questions about Ezobjectwrapperbundle
- What is Kaliop eZObjectWrapperBundle used for?
- It provides wrapper/view-model classes over eZ Publish 5 and eZ Platform content so you can expose intent-revealing getters instead of raw getFieldValue('title')->text calls. It centralizes attribute access, formatting, and relation logic in reusable PHP classes. It is a Symfony bundle for eZ-native applications, not a general Laravel package.
- Can I install kaliop/ezobjectwrapperbundle in a Laravel application?
- No. The package is a Symfony bundle that assumes eZ's kernel and content repository services; it has no standalone or framework-agnostic mode. Laravel has no eZ kernel, so the bundle's services and wrappers will not resolve. For Laravel, implement your own DTOs or use Laravel-specific content packages instead.
- Which Laravel versions are supported?
- None. This package does not target Laravel; it targets eZ Publish 5.x and early eZ Platform on Symfony 2.8/3.x and PHP 5.6/7.0. There is no Laravel service provider, facade, or compatibility layer. Do not expect Laravel 8, 9, 10, or 11 support.
- How do I install and register the bundle?
- Mechanically it is a Composer package, but you need a legacy eZ Publish/Platform Symfony app with matching PHP and Symfony constraints. Install via Composer and register the bundle in the Symfony kernel per the README, then define wrapper classes and mapping. On a modern Ibexa install, dependency resolution will likely fail or force unacceptable downgrades.
- Is it compatible with modern eZ Platform or Ibexa DXP?
- No, not cleanly. The last tagged release is from November 2017, targeting eZ Publish 5 and early eZ Platform; eZ Platform became Ibexa DXP and moved through Symfony 4/5, PHP 7.4/8.x, and breaking Public API revisions. Its Composer constraints will not resolve against current ezsystems or ibexa packages without a fork. Treat it as legacy-only.
- What are the licensing implications of GPL-2.0?
- Kaliop eZObjectWrapperBundle is GPL-2.0, a strong copyleft license. Internal, non-distributed use is often tolerable, but shipping it in a distributed product or appliance usually triggers source-disclosure obligations and needs legal review. In many commercial contexts this alone disqualifies the dependency.
- Is the package maintained and production-safe?
- Maintenance is effectively absent: roughly 9 stars, 0 dependents, and no release in about eight years. There is no security process, disclosure channel, or patch cadence. For production, that means high abandonment and upgrade risk; only consider it in a quarantined legacy deployment with a planned exit.
- What alternatives should I consider for cleaner eZ or Ibexa content access?
- On modern Ibexa, use the native view layer with content views, view models, and typed controllers, which closes much of the gap this bundle targeted. Alternatively, write thin internal DTOs plus a small factory or service to wrap content and relations; that is typically a few days of work with zero license surface. Forking and porting this bundle is possible but means permanent self-maintenance.
- How should I test wrapper classes if I inherit this bundle?
- There is no maintained CI signal beyond the 2017 tag, so you need your own test suite. Unit-test wrapper getters and formatting with mocked eZ content and field objects, and add integration tests against a pinned legacy eZ stack. Keep wrappers behind your own interfaces so you can replace the bundle later.
- Can I use it in a headless or non-eZ Symfony app?
- No. The bundle assumes a Symfony application running eZ's kernel with eZ content repository services in the container. It has no standalone mode, no framework-agnostic adapter, and no path to a headless or non-eZ consumer. Any other stack is out of scope.
Weaver
How can I help you explore Laravel packages today?