Native Divi modules and dynamic content
This page is the canonical reference for “module overrides” in current documentation: Divi 5 expects you to bind data on the native module in the Visual Builder using Divi’s Insert Dynamic Content (and Machine’s field providers in the dynamic picker), not a separate “override this module globally” flow in Machine settings.
There is no standalone customer doc titled “Module overrides” beyond this page and the Complete feature list inventory. Older guides that pointed only at Divi Engine → Machine → Settings for map pins are legacy; see ACF Map One Pin for the updated steps.
Map pins (Divi 5)
For Map, Map Pin, and Fullwidth Map, choose your ACF (or other supported) Google Map field through Insert Dynamic Content on the module’s map / location fields so each template and each post in context gets the correct coordinates.
Why this replaced the old settings-first story: New builds stay predictable—each Theme Builder template declares which field feeds the map. A legacy optional path still exists in the plugin: when Machine → Settings has a global map field and post type configured and the viewed post matches that type, the runtime can still merge lat/lng into map blocks for backwards compatibility. Do not rely on that for new Divi 5 work; configure the module directly.
For archive pages with many markers, keep using ACF Map Multiple Pins patterns (Archive Loop + map module id) alongside per-row dynamic content where needed.
Post Slider extensions
Post Slider and Fullwidth Post Slider gain Machine-aligned query and targeting (post types, taxonomies, meta-style constraints) so listing and detail templates can reuse the same mental model as Archive Loop without replacing the core slider module. Details live in the Post Slider module reference.
Gallery, counters, video, countdown
Recent releases add Insert Dynamic Content on native Gallery, Circle Counter, Number Counter, Bar Counter, Video, and Countdown so listing pages, singles, and Theme Builder bodies can pull custom field (and related) values without swapping in a dedicated Machine module everywhere.
- For rich field-backed sliders, grids, lightbox grids, and repeater-driven galleries, the Gallery/Slider Machine module remains the right tool—see Image gallery (free ACF) and Image gallery (ACF Pro).
Inline field tags ({dm:…})
Settings → General (Divi Engine hub) supports optional {dm:field_name}-style placeholders inside module text fields so simple values can render without opening the dynamic picker on every text node. Treat this as a lightweight shortcut, not a replacement for Insert Dynamic Content on structured modules (maps, media, dates). Field names must match your registered field keys; scope is text-oriented modules that pass content through Machine’s replacement pass.
Optional global Countdown (settings)
Machine → Settings may still expose options used for a global Countdown date source when the layout does not set one—separate from the per-module Insert Dynamic Content path on Countdown. Prefer module-level dynamic content for new Divi 5 templates when you need explicit control per layout.
What's next
- Complete feature list — Full inventory of modules, filters, tools, and extensions.
- ACF Map One Pin — Single-pin map setup with Divi 5 steps.
- Key capabilities — Pillar overview linking into Features and Modules.
- Custom field ecosystem — Supported field providers and terminology.