Custom fields and providers
Divi Machine is built around a custom field ecosystem, not a single vendor. On Divi 5, the plugin looks at which field stacks are active and exposes the same Custom Field Item, Repeater / Table / Tabs, Gallery / Slider, and filter facets across them so agencies can standardize on one module set.
Supported stacks (examples)
When these plugins (or their forks) register fields WordPress-wide, Machine can read and render them in Custom Field Item and related modules, and surface compatible facets in Filter Posts Item where the field bridge applies:
- Secure Custom Fields and Advanced Custom Fields
- Pods
- Meta Box
- Toolset
- ACPT (Advanced Custom Post Types)
Exact coverage depends on field type and what each provider registers; if a type is uncommon, start with a test row in a loop layout before committing a whole archive design.
What you do in the builder
- Pick the field — Add Custom Field Item, choose Custom field source (current post, user, term, options page, relationship context, and so on), then set Custom Field Name to the field slug the provider shows in WordPress.
- Compose layouts — Use Repeater / Table / Tabs for parent fields and nest Custom Field Item children for sub-rows; use Gallery / Slider when the stored value is gallery-like or image sets.
- Filter the same data — On archive pages, wire Archive Loop to a Filter Posts bank; field-backed controls reuse the same mental model as the display modules (Ajax Filter features for UI depth).
Related guides
- Custom Field Item — Full module reference (settings reference).
- Custom Field Item conditional logic — Visibility, empty values, and CSS-class tricks.
- Linked post types — Relationship-driven listings that pair with field modules.
What's next
- Key capabilities — Pillars map: archives, search, extensions, bundled filter stack.
- Divi 5 vs Divi Machine — What Divi core ships versus Machine-native and bundled modules.
- Repeater, table, and tabs — Layout patterns built from nested Custom Field Items.