Weave Code
Fieldtype Query Laravel Package
ibexa/fieldtype-query
Ibexa Query Field Type lets content managers map an executable Repository Query directly to a content field, making dynamic, query-driven content easy to configure within Ibexa DXP. Part of the Ibexa DXP package suite.
At a glance
Frequently asked questions about Fieldtype Query
- Is ibexa/fieldtype-query a Laravel package I can install with Composer into a Laravel app?
- No. This is an Ibexa DXP Field Type that extends the Ibexa content model and Repository API, so it only works inside an Ibexa DXP installation. Installing it in a plain Laravel application gives you nothing to bind to, because Laravel has no Ibexa content types, field definitions, or Repository Query layer. If your Laravel app needs this functionality, run Ibexa DXP as a headless content service and consume query results over Ibexa's API or GraphQL instead.
- Does the Query Field Type support Laravel or only Ibexa DXP?
- It supports Ibexa DXP only. There is no Laravel service provider, config file, or facade in the package; the integration surface is the Ibexa Field Type registry and the admin UI. Laravel teams typically meet it indirectly when a front end pulls Ibexa content through GraphQL or REST, but the package itself stays server-side in Ibexa.
- Which Ibexa DXP versions does ibexa/fieldtype-query support, 4.6 or 5.x?
- Both lines exist, but they are not interchangeable. The 5.x line targets PHP 8.3 and Symfony 7.x and removes deprecated REST-related code, while 4.6.x remains the older supported line. Match the package major to your Ibexa DXP major, and regression test admin UI, GraphQL, and any custom field templates after upgrading.
- How do I install and enable the Query Field Type in Ibexa DXP?
- Install it with Composer inside an existing Ibexa DXP project, then make sure the bundle is registered and the Field Type is available in your content type definitions. From there you add the Query field to a content type and configure the query settings through the editor interface. The README assumes a working Ibexa DXP install first, so set that up before adding this package.
- What PHP and Symfony versions does version 5.x of the Query Field Type require?
- Version 5.x requires PHP 8.3 and Symfony 7.x, aligning with the current Ibexa DXP release line. Older 4.6.x releases support the previous PHP and Symfony combinations. Check your platform's composer.json and CI matrix before upgrading, because a major-version bump here usually forces an upgrade of the whole Ibexa stack.
- How does a content manager map a Repository Query to a field in Ibexa?
- After the Field Type is added to a content type, editors configure the field in the admin UI and select or define the Repository Query it should execute. The stored query then resolves when the content is rendered or requested through the API, so results stay dynamic without developer involvement. This is the main benefit: reusable queries live in the content model instead of being hardcoded in templates or controllers.
- How do I stop editor-authored query fields from slowing down my Ibexa site?
- Treat editor-authored executable queries as a performance risk and add guardrails before rollout. Practical controls include result limits, pagination, a query allowlist, preview-only roles, approval workflows, execution timeouts, and audit logging of changes. Pilot on one low-risk content type with a handful of queries and keep template or controller fallbacks until caching behavior is proven.
- What are the security and permission considerations for query fields?
- Query fields execute against the Ibexa Repository API, so permissions, content visibility, and query scope must be modeled deliberately. A field can only be as safe as the query behind it, and the package does not replace platform-level authorization or auditing. Decide who may create or edit query fields, review what content those queries can expose, and log changes to support incident review.
- Does the Query Field Type work with GraphQL and REST in Ibexa DXP?
- GraphQL support exists and has received field-resolution fixes, so verify the exact behavior on your Ibexa version rather than assuming parity with built-in field types. REST support changed in the 5.x line, which removes deprecated REST-related code, so downstream consumers relying on REST field data need checking. Test both surfaces in staging if external clients read query field values.
- What license applies to ibexa/fieldtype-query, Ibexa BUL or GPLv2?
- The package is dual-licensed: the Ibexa Business Use License, available with a valid Ibexa DXP subscription, or GPLv2 as a copyleft alternative. Composer metadata may report NOASSERTION, so confirm terms with procurement or legal rather than relying on the automated license field. If you hold an Ibexa DXP subscription, confirm the field type is covered; otherwise review GPLv2 obligations before adopting it.
Weaver
How can I help you explore Laravel packages today?