Compatibility and limits¶
Compound Field uses the field types provided by your installed modules. See available field types for common choices and required modules.
Boundaries that affect a design¶
| Capability | Supported scope |
|---|---|
| Outer cardinality | One, a finite number, or unlimited compound items. |
| Sub-field cardinality | A finite cap of at least one. More slots require more database columns. |
| Nesting | Compounds can contain other compounds; cycles and schemas beyond the column budget are refused. |
| Translation and revisions | Values follow the host. There is no independent revision or translation entity per compound item. See translation and moderation. |
| Sub-field configuration | Sub-fields share the compound definition. They do not each have a separate exported field configuration. |
| Core Migrate | A process plugin accepts the documented nested wire shape. |
| Feeds | No Compound Field target plugin is provided. |
| Layout Builder | Host compound blocks and optional sub-field blocks. No layout editor for a compound's own internal display. |
| Composition | Use the Composition tab or the includes configuration key to share sub-field definitions. |
Changes can remove history¶
Removing a populated sub-field or lowering its cap can destroy values in current and historical revision tables, across every field using the compound. The UI requires explicit consent. A normal content revision cannot recover dropped columns. Keep a database backup and use the removal tutorial.
Deleting a host field leaves deleted data awaiting purge. The compound must stay installed until purge finishes. Remove a compound in order.
Contrib and release status¶
Sub-field widgets, formatters and field-type plugins still need evaluation with
your site's settings. A contrib feature that expects its own persisted
field.field.* configuration may need explicit integration.
Entity Reference Revisions can retain orphaned paragraphs held through a compound. The upstream purger does not recognize every composite parent field. Keep that storage cost in mind when choosing revision references.
Compound Field is pre-alpha. Features and configuration may change between versions. Rehearse upgrades and structural changes on a copy of the site.