Typing the post title into a heading works until the title changes. Then it is wrong on one page, and nobody notices for a month.
Dynamic content puts a live field in place of typed text: the block shows whatever the value is now.
Before You Start
- Edition: Pro — dynamic content needs Nexter Blocks Pro.
- Block to enable: any Nexter block, switched on under Nexter > Blocks in your WordPress dashboard.
- A block with a text field — a heading or a button, for example.
Video Tutorial
Steps
- Select a block and put the cursor in the text field you want to make dynamic.
- Open the dynamic content option for that field.
- Choose the field — a post value, a site value, or a product field.
- Publish and check the real page. The editor shows a placeholder; the published page shows the value.
How It Behaves
The field is stored as a placeholder in the block’s markup and swapped for the real value when the page is rendered.
- Measured on published pages. A heading set to the post title rendered the page’s actual title; set to the post date it rendered
2026-09-21 05:59:32; set to the site title it rendered the site’s name. - The placeholder never reaches the visitor when Pro is active — measured, the
data-tpgb-dynamicattribute is gone from the output entirely. - Post, site and WooCommerce product fields are available — titles, slugs, excerpts, dates, post type and status, site title, tagline and URL, and product price, SKU, stock, rating and terms.
- An unavailable field renders as nothing. Measured with a field name that does not exist: the placeholder was removed and empty output was left behind, with no warning. A heading can silently become blank.
- Measured with Nexter Blocks Pro deactivated: the placeholder is not replaced — see the limitations below, because this one does not fail quietly.
Limitations
- Pro only, and it does not fail quietly. Measured with Nexter Blocks Pro deactivated: the placeholder is not replaced, so visitors see the literal placeholder text on the live page. If a Pro licence lapses, dynamic fields become visible placeholder text rather than nothing. This is reported to the development team.
- An empty field leaves an empty block. A post with no excerpt gives you a heading with nothing in it — check posts that are missing the field.
- It reads the current post. Inside a listing or template it follows the item being rendered; on a static page it reads that page.
- Product fields need WooCommerce and a product context. On an ordinary page there is no product to read.
- The editor shows a placeholder, not the value, so layouts have to be checked on the published page — a long real title can wrap where the placeholder did not.
Troubleshooting
My heading is empty on the published page
The field has no value for that post, or the field is not available in that context. Measured, an unavailable field renders nothing at all rather than an error.
I can see the placeholder text on my live site
Nexter Blocks Pro is not active. Measured, the placeholder is only replaced with Pro active; without it the raw placeholder is shown to visitors. Check your licence and activation.
The product price is not showing
Product fields need WooCommerce active and a product to read. They will be empty on a normal page.
It shows the wrong post’s title
Inside a listing the field follows the item being rendered. Check which block the field sits in.
It looks fine in the editor but wrong when published
The editor shows a fixed-length placeholder and the real value can be much longer. Always check the published page.
