GoBuildWP

Page buildersPro

GoBuildWP Divi integration: requirements and coverage

Divi 5 saves a page as divi/ blocks in post_content, and this page lists the Divi MCP abilities GoBuildWP offers against that document and against the records around it: global presets, colours, fonts and variables in option rows, Divi Library posts, and Theme Builder templates. Each group says what it changes and whether the change log can take it back.

AI clientyour-site.comVerify site policy

Under the intro on the Work page, show the three newest case studies with their titles.

  1. wppilot/divi-get-contentRead

    Returns the page as addressed nodes. Compare the target with divi-list-modules and select a loop_capable container or module; divi/blog has its own query and does not accept this loop.

  2. wppilot/divi-list-loop-query-typesRead

    Lists the query types a loop can use, including post type queries for the case study type.

  3. wppilot/divi-enable-loopWrite

    Turns the discovered loop-capable node into a loop over the three newest case studies. Use its returned address; the page is snapshotted before the write.

  4. wppilot/divi-apply-dynamic-contentWrite

    Uses the separately discovered child heading's address and supported title field to bind the post title source, then verifies that each iteration prints its own case study.

Proposed sequence from source declarations; not a recorded task or proof of client compatibility. Inspect saved state and browser or provider results separately.
Edition
Pro
Abilities
47
Requires
WordPress 6.9+, PHP 8.0+, Divi 5.0+

Requirements and coverage

What this integration needs, and where the detail lives

Edition
Pro
WordPress and PHP
6.9+ and 8.0+
Version floor
Divi 5.0+
Abilities
47, listed in the reference

Data model

Blocks in post content, flags in post meta

In Divi 5 the layout is a tree of divi/* blocks stored in post_content, with a fixed skeleton: section, row, column, then leaf modules, and row-inner and column-inner for nesting. GoBuildWP parses those blocks into nodes of name, attrs and children and addresses each by a slash path of indexes, such as 0/1/0. Three meta flags travel with the content: _et_pb_use_builder, _et_pb_use_divi_5 and _et_pb_show_page_creation. GoBuildWP writes them the way Divi's own save does, because a page missing _et_pb_use_builder gets wrapped in a placeholder the first time the Visual Builder opens it, and the build is lost to _et_pb_old_content.

Around the page, Divi keeps global colours and fonts in its theme options, variables and presets in their own option rows, and Library items as et_pb_layout posts. A Theme Builder template is three kinds of record at once: an et_template post, one layout post per area (et_header_layout, et_body_layout, et_footer_layout), and a link from the Theme Builder container. Its conditions are stored one per meta row.

Worked example

A loop of recent case studies on an existing page

Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.

A loop that updates itself as case studies are published. If a module is deleted earlier in the same session, later addresses shift, so the agent reads the tree again before the next edit.

Reread the structure before any path-dependent follow-up. Finish the loop example in the native builder and rendered browser page.

  1. divi-get-content

    Returns the page as addressed nodes. Compare the target with divi-list-modules and select a loop_capable container or module; divi/blog has its own query and does not accept this loop.

  2. divi-list-loop-query-types

    Lists the query types a loop can use, including post type queries for the case study type.

  3. divi-enable-loop

    Turns the discovered loop-capable node into a loop over the three newest case studies. Use its returned address; the page is snapshotted before the write.

  4. divi-apply-dynamic-content

    Uses the separately discovered child heading's address and supported title field to bind the post title source, then verifies that each iteration prints its own case study.

Limits

Divi constraints and undo gaps

  • The module needs Divi 5.0 or later. Divi 4 shortcode layouts are not edited here.
  • Input trees are capped at 64 levels deep and 2,000 nodes, so a runaway structure is refused before it reaches post_content.
  • Creating or deleting a Theme Builder template, and deleting a Library item, cannot be rolled back from the change log.
  • Divi builds its CSS at render time, so a successful write still needs a look at the page.

Questions

Divi questions

Why does GoBuildWP write Divi's builder flags on every save?

Divi treats a post without _et_pb_use_builder as classic content. The first Visual Builder open then wraps the layout in a placeholder and moves the original aside, which looks like the build vanished. Writing the three flags as Divi does prevents that.

Can the agent change where a Theme Builder header appears?

Yes. divi-set-theme-builder-conditions replaces the include and exclude conditions on the template, using ids from divi-list-theme-builder-conditions, and that change can be rolled back.

Is a Divi preset change undoable?

Yes, presets are option rows and the ledger restores the row. Until you roll it back, every module using the preset shows the change.

Can WooCommerce state hide a Divi module?

Display conditions include purchase history, cart contents and stock state when WooCommerce is active, alongside login, role, date, device and cookie rules.

Divi 5 has a vendor AI agent. An embedded builder assistant and GoBuildWP's externally connected MCP module are different workflows; check module, preset and Theme Builder coverage for your version. Divi AI Agent documentation

Where these facts come from

GoBuildWP behaviour is taken from the plugin source and the ability reference; third-party details from the vendor documentation below, checked by the GoBuildWP team.

Divi is a separate product; no partnership or endorsement is implied.

Try it on Divi in Read Only first