Weave Code
Layouts Ezplatform Laravel Package
netgen/layouts-ezplatform
Integrates Netgen Layouts with eZ Platform, enabling editors to build and manage page layouts using eZ content, site structure, and reusable blocks. Provides content-aware layout components and configuration to embed dynamic layouts into eZ Platform sites.
Netgen Layouts & eZ Platform integration
Frequently asked questions about Layouts Ezplatform
- Does netgen/layouts-ezplatform work with Laravel?
- No. This is a Symfony bundle that bridges Netgen Layouts to eZ Platform (now Ibexa DXP); there is no Laravel service provider, no Eloquent adapter, and no usable surface outside an Ibexa kernel boot. Its layout resolvers, block handlers, and item view providers all read the Ibexa content repository, so installing it in a Laravel app gives you nothing to call. If your requirement is layout composition in Laravel, evaluate Netgen Layouts standalone or a headless page builder instead.
- How do I install netgen/layouts-ezplatform?
- Install Netgen Layouts core first, then require this adapter with Composer and register the bundle in your Ibexa kernel. Standard Symfony bundle registration and configuration apply, plus siteaccess-aware template and block configuration. Netgen Layouts introduces its own schema for layouts, zones, blocks, and rules, so plan the migrations and a database review rather than assuming a read-only bolt-on.
- Which eZ Platform and Ibexa versions are supported?
- Support is tied to a specific Netgen Layouts major paired with a specific Ibexa major, typically Ibexa 3.3 LTS or 4.x. Legacy eZ Platform 2.x is end of life, so on that stack the package is effectively moot until an upgrade lands. Always check the vendor's supported-version matrix and pin exact versions in composer.json instead of relying on loose constraints.
- What PHP and Symphony versions do I need to run it?
- Expect PHP 8.1 or newer, Symfony 5.4 or 6.x, and Doctrine, all inherited from the Ibexa release you are running. Because the adapter must match both a Netgen Layouts major and an Ibexa major, the PHP and Symfony versions are effectively pinned by that pair. Treat version upgrades as coordinated events tied to Ibexa's release cadence rather than independent Composer updates.
- What does this package actually add on top of Netgen Layouts core?
- It supplies the Ibexa-specific glue: layout resolvers that map content, location, section, and siteaccess rules to layouts, block handlers that read the Ibexa content repository, item view providers, and the administration UI wiring for creating and editing layouts. Editors build and manage layouts inside the eZ Platform admin while content stays managed in eZ Platform. Without Ibexa, the adapter has nothing to talk to, which is why Netgen Layouts core remains the reusable part.
- What are the alternatives to netgen/layouts-ezplatform?
- On Ibexa, Ibexa Experience ships its own page builder, so the first comparison is native versus Netgen Layouts. Netgen Layouts wins specifically for rule-based, cross-content-type, multi-site layouts applied without per-object authoring, so confirm that is genuinely your requirement before running two layout systems. Off Ibexa, evaluate Netgen Layouts core standalone or a headless page builder, since porting this adapter to another framework means rewriting it.
- What license does it use and can I ship it in a closed-source product?
- The package is GPL-2.0, which is copyleft and material for any proprietary or redistributed product. Adoption requires legal sign-off against your distribution model before you write integration code. If you intend to ship closed source, budget for a commercial license from Netgen rather than assuming the open-source license covers you.
- What should I check before putting it into production?
- Design caching and invalidation before broad rollout, because layouts render through your existing HTTP cache layer and rule changes need a clear purge path. Review the extra layout, zone, block, and rule tables with your DBA and fold them into migration and backup procedures. Roll out per siteaccess, starting with a non-production siteaccess and two or three representative layout rules, then validate rendering and editorial UX before going wider.
- How do I test upgrades and avoid breaking the integration?
- Add CI that resolves the actual version matrix and boots the Ibexa kernel, because container compilation is where version skew surfaces first. Most failures appear as a DI container compile error or, worse, a missing block handler at render time rather than a clean Composer conflict. Model a couple of real layout rules in a test siteaccess and assert the rendered output so a silent handler regression fails the build.
- Is netgen/layouts-ezplatform actively maintained?
- It is vendor-backed rather than abandoned, but the community signal is weak: roughly 14 stars and no dependents, so the bus factor is your relationship with Netgen, not the ecosystem. Expect low community throughput and plan to maintain against upstream yourself between vendor releases. Ask whether this adapter is inside your commercial support scope and whether the vendor roadmap tracks Ibexa's, given Ibexa's own page builder.
Weaver
How can I help you explore Laravel packages today?