Weave Code
Fieldtype Matrix Laravel Package
ibexa/fieldtype-matrix
Matrix Field Type for Ibexa DXP and Ibexa Open Source adds configurable matrix fields to content types, letting editors define rows and columns of data. Licensed under Ibexa BUL or GPLv2.
At a glance
Frequently asked questions about Fieldtype Matrix
- Can I install ibexa/fieldtype-matrix in a Laravel application?
- No. This is an Ibexa DXP field type bundle that extends Ibexa's content model, and Ibexa DXP is built on Symfony, not Laravel. It registers itself into Ibexa's field type registry, admin editing UI, Doctrine persistence layer and search indexing, so it has nothing to hook into inside a Laravel app. If your stack is Laravel, treat this as the wrong platform and meet the requirement with a JSON column, a custom table, or a dedicated matrix package instead.
- What does the Ibexa Matrix field type actually do?
- It adds a configurable matrix field to Ibexa content types, letting editors fill in rows and columns of values inside a content item. Typical fits are pricing grids, specification tables and availability matrices where the tabular structure belongs in the content model rather than in free-form HTML. It is the native way to add structured tabular data in Ibexa, with no core hacks or forking required.
- How do I install and enable the Matrix field type in Ibexa DXP?
- Install it with Composer using composer require ibexa/fieldtype-matrix, then register the bundle alongside your other Ibexa bundles and clear the cache. After that you add the Matrix field type to a content type definition and editors can start authoring matrix content. The mechanical steps are quick; the real effort is content-model design, template rendering and editorial training.
- Which Ibexa DXP and PHP versions does ibexa/fieldtype-matrix support?
- The bundle version line tracks the Ibexa DXP release line, so you must confirm the exact constraint in composer.json against your installed DXP version before pinning. Upgrading one typically forces an upgrade of the other, so plan DXP and bundle upgrades together. Also verify the listed release date in the registry, since a future-dated tag has been observed and should be checked against the actual changelog and tags before you commit.
- What license does ibexa/fieldtype-matrix ship under, and is it safe for commercial use?
- It is dual-licensed under the Ibexa Business Use License, which requires an active paid Ibexa DXP subscription, or GPLv2. GPLv2 is copyleft and is generally acceptable for internal or self-hosted use under the Ibexa Open Source edition, but obligations around distribution or SaaS exposure should be confirmed by legal counsel. The registry reports NOASSERTION, so automated license scanners may flag it and block your build until you obtain written clarification.
- How do I render Matrix field data in a Twig template?
- You render it like any other Ibexa field: access the field value object in your content template and loop over its rows and columns to output a table. In practice you will write custom Twig for headers, row labels and per-cell formatting that matches your design system. Check the bundle's shipped field type templates and Ibexa's field type rendering documentation for the exact value API in your DXP version.
- Where is Matrix data stored, and will it be indexed for search?
- Values are persisted through Ibexa's standard field storage via Doctrine, so the matrix lives as field data on the content item rather than in its own table. Indexing follows Ibexa's field type indexing behaviour for Solr or Elasticsearch, so you should verify how cell values are indexed in your setup. For very large matrices, test cell counts per content item and confirm indexing behaviour before going live.
- Is Matrix field data available through the REST API or GraphQL?
- As an Ibexa field type, the matrix is expected to be exposed through Ibexa's REST and serialization layer alongside other field types. Whether a dedicated GraphQL schema or REST converter exists for matrix values depends on the bundle and your DXP version, so test serialization on a staging install. If headless delivery matters, validate this early rather than after the content model is built.
- Is ibexa/fieldtype-matrix production-ready given it has only 4 stars and zero dependents?
- Low Packagist popularity is normal for vendor-maintained DXP bundles, which are distributed through the Ibexa ecosystem rather than Composer discovery, so it is not evidence of poor quality. What it does mean is no independent community validation, no third-party tutorials and no external bug-fixing mass, so your own testing and vendor support carry the weight. Treat it as production-capable inside an Ibexa estate, but pin versions and have a rollback plan.
- What are the alternatives to the Matrix field type, and how do I get the data out later?
- Outside Ibexa, the alternatives are a JSON or text column, a custom entity or table, or a general-purpose matrix library, any of which is cheaper if you only need to store a 2D array. Inside Ibexa, a JSON or text field avoids the extra bundle but loses the structured editing UI and indexing. Note that matrix data lives in Ibexa's field storage with no neutral export format, so leaving the field type later means an extraction and re-modeling project you should scope up front.
Weaver
How can I help you explore Laravel packages today?