- Is se7enxweb/layouts-ezplatform-relation-list-query a Laravel package?
- No. Despite being listed among PHP and Laravel packages, it is a Symfony bundle for eZ Platform and Ibexa that supplies a Netgen Layouts query handler. It has no Illuminate service provider, no Laravel package discovery manifest, and no integration with Laravel's container, config, or Eloquent layers. Treat it as part of your legacy CMS boundary rather than your Laravel application code.
- How do I install the relation list query bundle in eZ Platform or Ibexa?
- Require it with Composer in an application that already has Netgen Layouts installed, then register the bundle in your Symfony kernel or bundles.php. Installation is conventional for eZ Platform bundles: a Composer requirement plus manual bundle registration. There is no Laravel-style auto-discovery, so you must wire it up yourself. Confirm your eZ Platform or Ibexa kernel and Netgen Layouts versions satisfy the declared Composer constraints first.
- What does a relation list query actually do in Netgen Layouts?
- It lets a layout block pull items from a relation list field type stored on any content item in the CMS. Instead of hardcoding which entries appear, editors maintain the relation list on the content item and the query resolves those relations at render time. The result is a block that stays in sync with editorial choices made in the CMS without template changes.
- Can I use this package inside a Laravel application with an adapter?
- Not in any practical sense. It depends on the eZ Platform or Ibexa kernel and the Netgen Layouts query and block model, so adopting it in Laravel would mean running a Symfony/eZ kernel alongside your Laravel app. That is a disproportionate architectural cost for a single query handler. The pragmatic path is to consume Ibexa content and relations over REST or GraphQL and keep this package out of your Laravel dependency graph entirely.
- Which PHP, Symfony, eZ Platform, Ibexa, and Netgen Layouts versions are supported?
- The supported matrix is not documented in the package overview, so verify it from the composer.json constraints before planning any upgrade. Legacy eZ-era packages frequently pin Symfony 5.x and PHP 7.4 or 8.0-era dependencies, which can collide with a modern security patch floor. Run composer why and composer outdated --direct against your target PHP and Symfony minor to resolve the effective dependency set before you attempt anything.
- How do I configure a block to list content from a relation list field?
- Add the relation list query as the query type for a Netgen Layouts block and point it at the content item that holds the relation list field. The query then resolves the referenced items and passes them into the block's template for rendering. Exact configuration parameters depend on the handler, so check the bundle source and the upstream Netgen Layouts query documentation for the available options.
- What changed between version 1.4.1 and 1.4.2?
- The 1.4.2 release ships with an empty changelog body and only an auto-generated compare link. A patch bump with no described changes is not reviewable, so you cannot distinguish a no-op tag from a behavior change in query construction or result ordering. Read the commit diff line by line before moving a production content-rendering dependency to it.
- Does this query handler affect result ordering, pagination, or visibility filtering?
- Any change to query construction in a layout handler can alter ordering, paging, or which items get filtered out, and that is user-visible layout output. That is exactly why an undescribed patch release is a concern for this package. Diff releases against your rendered output and pin the version you have validated instead of floating the constraint.
- What is the alternative for related-content listings in a Laravel app?
- Expose Ibexa content and relations through its REST or GraphQL API and model the related-content listing in Laravel with Eloquent or your own query layer. That keeps the legacy CMS at the boundary, gives you Laravel-native caching and testing, and avoids dragging a Symfony/eZ kernel into your application. If you are mid-migration to Ibexa, prefer Ibexa-native query types over a small third-party fork.
- Who maintains this package, and is it safe to run in production?
- It is published by se7enxweb, a small fork organization, and appears to be a downstream derivative whose upstream must be tracked separately, so the bus factor is likely one. Pin exact versions, review each release diff, and avoid adding it to a platform you are actively migrating away from. Check the license and run composer audit for advisories against it and its transitive dependencies before adopting it.