Skip to Content
TroubleshootingPage BuildersDivi

Divi

Divi is the most common cause of Structura posts rendering with only a title and featured image on the front end. This page explains why, what Structura fixes automatically, and what you should check on your site to make sure nothing else is interfering.

What’s happening

Divi attaches to WordPress’s the_content filter. When it sees a post that it thinks was built in the Divi Builder, it replaces the default rendering with its own shortcode loader. Whether Divi “thinks” a post is a Divi post depends on a single meta flag: _et_pb_use_builder. When the flag is on, Divi takes over; when it’s off, Divi stays out of the way and WordPress renders the post normally.

Divi has an option labelled Default Editor (under Divi → Theme Options → Builder → Post Type Integration). If this is set to Divi Builder for the Posts post type, Divi’s save_post handler auto-writes _et_pb_use_builder = on to every new post created by any plugin — including Structura. The result: the front end renders a blank body.

What Structura does automatically

As of the 2026-04-23 release, every Structura post is created with _et_pb_use_builder = off written atomically as part of the wp_insert_post call. This detail matters: WordPress guarantees that meta passed via meta_input on insert is persisted before save_post fires, so Divi’s own save-handler sees a populated meta and skips its auto-enable branch. The flag wins the race.

You shouldn’t have to change anything in your Divi settings for Structura posts to render correctly on the front end. If the body is still blank after you’ve updated Structura, keep reading — the cause is usually a Divi Theme Builder template, not the per-post flag.

How to verify your Divi Theme Builder template still renders

post content

Divi has a separate feature — Theme Builder — that replaces the theme’s PHP templates with Divi layouts. A Theme Builder Post Template assigned to your posts is rendered instead of the theme’s single-post layout; if that template doesn’t include a module that pulls in post_content, the front end will be blank no matter what the _et_pb_use_builder flag says.

Walk through this to check:

  1. In wp-admin, go to Divi → Theme Builder.
  2. Look for a template titled All Posts, Posts in category X, or similar. If there’s no custom post template, Divi uses your theme’s default — skip to the next section.
  3. Open the post template. Look at the Body area of the layout.
  4. The body must contain a Post Content module (a dynamic module that outputs whatever WordPress stored in post_content) — not just a Text module with hardcoded text, and not just a collection of images/titles. If the Post Content module is missing, the front end will never show your post’s text.
  5. If the Post Content module is present, click it and confirm its Content Source is set to For Current Post (not a specific post ID).
  6. Save the template and reload the front-end URL of a Structura post.

If your Theme Builder template doesn’t include a Post Content module, add one, save, and reload. This is the single most common site-configuration reason Structura posts render blank after the automatic fix is in place.

What to check if the body is still missing

After confirming the Theme Builder template, work through these in order:

  1. Clear all caches. Divi ships with its own static file cache plus a dynamic-assets cache. Go to Divi → Theme Options → General and click Clear all caches. If your site also uses a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed), flush that too. Stale cached HTML is a very common cause of “I fixed the settings but the post is still blank.”
  2. Check the post in wp-admin. Open the post in the block editor. Click the three-dot menu at the top-right and choose Switch to draft, then Update, then Publish again. This forces Divi’s save-handler to re-run with the correct meta.
  3. Look at the _et_pb_use_builder meta directly. Install a meta-inspector plugin (e.g., “Post Meta Inspector”) or use WP-CLI wp post meta get <id> _et_pb_use_builder. The value should be off. If it’s on, something on your site is re-enabling it after Structura writes off — most commonly a custom save_post hook in a child theme or a third-party plugin.

Settings to leave alone

You don’t need to:

  • Change the Default Editor setting under Divi → Theme Options → Builder → Post Type Integration. Structura’s per-post flag overrides it for Structura posts.
  • Disable Divi globally.
  • Edit posts Structura has already created to switch them “back to the default editor” — the flag is already set correctly.

If your Default Editor is set to Divi Builder for Posts, manually-created posts will still open in the Divi Builder by default. That’s fine; it just doesn’t affect Structura’s posts.

If none of this helps

Contact support with:

  • Your Divi theme version (Appearance → Themes) and Divi Builder plugin version if installed separately.
  • Your active theme (it might be a Divi-based child theme).
  • The Theme Builder template in effect for the blank post — a screenshot of the template’s body area is most useful.
  • A link to the blank post on the front end.
Last updated on
BrizyElementor