Page buildersPro
GoBuildWP Flatsome integration: requirements and coverage
Flatsome's UX Builder has no JSON document: the shortcode markup in post_content is the whole model. These Flatsome MCP abilities read that markup as a tree, write it back by path, and leave alone what they were not asked to change. Below is what each call touches, why editor ids matter, and what the change log can restore.
The promo banner in our footer says Free shipping over 50. Change it to over 75.
wppilot/flatsome-list-blocksReadFinds the footer promo UX Block and its id, so the edit happens once instead of on each page.
wppilot/flatsome-get-contentReadParses the block's post_content; the text element holding the offer sits at path [0, 0, 1].
wppilot/flatsome-edit-elementWriteMerges the new text into that element only; its _id and siblings stay as they were.
- Edition
- Pro
- Abilities
- 11
- Requires
- WordPress 6.9+, PHP 8.0+, Flatsome 3.20.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
- Flatsome 3.20.0+
- Abilities
- 11, listed in the reference
Flatsome MCP guide: setup and worked tasks Flatsome ability reference (flatsome)
Data model
The markup is the model
A UX Builder page is ordinary shortcodes in post_content, section, row, col, text and the ux_ elements, with no per-element rows. Elements the editor has touched carry an _id attribute, and that id is the key into the _ux_builder_data post meta where the editor keeps its own per-element state. GoBuildWP preserves every _id on a round trip and does not copy one into a newly inserted element, because two elements sharing an id make the editor drop one of them.
Anything between shortcodes, loose HTML, block comments, or the flatsome/uxbuilder block wrapper on block-editor sites, becomes an html node and is written back byte for byte; the editor itself would convert loose text into text elements on open. Reusable sections are UX Blocks, posts of the blocks type with block_categories terms, embedded elsewhere through a block shortcode with the block's id. Flatsome compiles element CSS at render time and keeps no per-post cache, so there is nothing to purge after a write.
Limits
Flatsome refusals and floors
- The module needs Flatsome 3.20 or later; child themes report the parent's version.
- A breakpoint Flatsome does not define is refused in a responsive map rather than written as an attribute the theme ignores.
- These builder calls do not manage global header, typography or colour options. Theme Bridge reaches only eligible registered Customizer theme_mods; verify keys on the installed theme and use vendor controls for private Theme Options storage.
- Adding a new UX Builder element type is code in a theme or plugin; none of these abilities register elements.
Worked example
Changing a footer banner used on every page
Expected outcome to verify on the installed stack; this sequence has not been recorded as a runtime test.
Every page embedding the block shows the new threshold once it is built again; a page cache or CDN can keep serving the old copy until it is purged. The edit is recorded against the block's post, so a rollback restores the previous text everywhere at once.
The banner follows an already-approved shipping rule. Verify WooCommerce’s actual threshold separately if requested, then inspect the live footer and its delivery caches.
flatsome-list-blocksFinds the footer promo UX Block and its id, so the edit happens once instead of on each page.
flatsome-get-contentParses the block's post_content; the text element holding the offer sits at path [0, 0, 1].
flatsome-edit-elementMerges the new text into that element only; its _id and siblings stay as they were.
Questions
Flatsome questions
What is _ux_builder_data and should I worry about it?
It is post meta where UX Builder stores per-element state, keyed by each element's _id attribute. GoBuildWP keeps those ids intact, so the meta stays correct without being rewritten.
Why do my Flatsome pages keep their loose HTML after an agent edit?
Text and markup between shortcodes is carried as html nodes and emitted unchanged. UX Builder would convert it into text elements on open; GoBuildWP does not, so a small edit never reformats content you did not ask about.
Do I need to clear a cache after a Flatsome write?
Not for Flatsome itself, which compiles element CSS during rendering. A page cache plugin in front of the site may still need to purge the URL.
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.
Flatsome is a separate product; no partnership or endorsement is implied.