URLs, not attachment IDs
Most page builders reference an image by its attachment ID. Divi writes the full URL straight into the module's shortcode or block markup.
Integrations · Divi
Divi bakes image and background URLs directly into its shortcode and block markup instead of linking them by attachment ID the way most page builders do. A plain copy keeps those URLs pointed at the old site — PostDeploy Pro finds and rewrites them to the destination's real copies.
Most page builders reference an image by its attachment ID. Divi writes the full URL straight into the module's shortcode or block markup.
Responsive background image overrides for tablet and phone are separate values that also need rewriting, not just the default desktop background.
Divi 4 uses classic shortcode markup; Divi 5 is block-based. A fix built for one format's syntax misses the other entirely.
One honest exception: the Gallery module's attachment-ID list is resolved for Divi 4's classic module; Divi 5's gallery block format isn't handled yet.
Divi bakes image and background URLs directly into its shortcode (Divi 4) and block (Divi 5) markup instead of linking them by attachment ID the way most page builders do. A plain content copy keeps those URLs pointed at the source site.
Yes, the URL-based rewriting covers Divi 4's classic shortcode format and Divi 5's block format. One exception: the Gallery module's attachment-ID list is currently resolved for Divi 4's classic module; Divi 5's gallery block format isn't handled yet.
Those are resolved too, not just the default desktop background.
Why Divi's URL-based image references break a plain copy, the Gallery module's one exception, and what has to happen to fix it.
Divi resolution alongside ACF, Elementor, WPML, rollback, bulk & scheduled deployment, and automation.
Start free, or get Pro for Divi, ACF, Elementor, WPML, rollback, and automation.
PostDeploy Pro — stop copy-pasting content between WordPress sites.
Get Pro