Kadence Blocks ability reference
Reference for the GoBuildWP Pro 1.12.4 source. Installed schemas and policy remain authoritative.
This Kadence Blocks ability reference covers a catalogue and schema reader for every kadence/* block on a site. It writes nothing; posts are edited through GoBuildWP Free's block-editor abilities, and ready-made layouts through the separate Kadence patterns module.
Read-only, write and destructive groups describe the source annotations. They do not establish a minimum safety profile, human approval or undo support. Those controls are separate: check the installed ability, the connected user and the active site policy before calling it. A read can still return sensitive data. These pages are not evidence that every operation passed an end-to-end runtime test.
What Kadence Blocks needs before these load
Kadence Blocks must be active, with no version floor set by this module. Kadence Blocks Pro is optional. Unlike most block plugins' Pro editions, it does not get a namespace of its own: its blocks are registered as kadence/* alongside the free ones.
- Kadence Blocks editions
- free, pro
Telling free and Pro blocks apart
Since the names cannot say which plugin a block belongs to, the module looks at each block's render callback. A class from the Kadence Blocks Pro code (named Kadence_Blocks_Pro_ something, or under the KadenceBlocksPro namespace) marks the block as Pro; anything else is free. The check deliberately requires the underscore after "Pro", because the free Progress Bar block's class name also begins with Kadence_Blocks_Pro.
kadenceblocks-check-setup reports both plugins' versions and the count of free and Pro blocks, and its own instructions list the kind of block Pro adds: dynamic HTML and lists, post grid and query, repeater, modal, split content, advanced form blocks, header and off-canvas blocks, and a slider.
Catalogue and schema
kadenceblocks-list-blocks returns each block's name, title, family, category, whether it is dynamic, its attribute count and its nesting hints, and accepts family and name_contains filters (form, header, tab, accordion or query narrow it quickly). kadenceblocks-get-block-schema returns the full attribute schema of one block, such as kadence/rowlayout, and answers kadenceblocks_not_found outside the kadence/* namespace. The most common nesting mistake it prevents: a column needs a row layout ancestor, and one placed anywhere else renders but breaks the row.
Before accepting the result
Enable batch finalization, open and verify the logged-in runtime tab, then poll the pending batch until finalized or an error state. Inspect the native editor and rendered pattern before completion.
Example Kadence Blocks input: wppilot/kadenceblocks-get-block-schema
This one operation declares the 1 top-level input parameters below in wppilot-pro/includes/wppilot-abilities/wppilot-kadenceblocks/wppilot-get-block-schema.php; name is required. Other calls in this module take different arguments. Nested schemas and constraints are not expanded here; the complete live schema a connected client discovers is authoritative.
| Parameter | Type and meaning |
|---|---|
namerequired | string. Full block name, e.g. "kadence/rowlayout" or "kadence/postgrid". Must be in the `kadence/*` namespace. |
Representative call sequence
This sequence describes the documented calls and checks to perform. It is not a recorded result from an installed WordPress site. Inspect returned errors and partial results, then verify the saved values and affected output before proceeding.
Add a two-column row to a post built with Kadence blocks.
- 01
wppilot/kadenceblocks-list-blocksFiltered by name to rowlayout and column, to confirm both are registered and how they nest. - 02
wppilot/kadenceblocks-get-block-schemaReturns the row layout's attributes, including the column settings the block spec must use. - 03
wppilot/gutenberg-get-contentReads the post's current block tree, so the row goes in the intended place. - 04
wppilot/gutenberg-add-pending-changeQueues the new row for finalisation in the block editor, where Kadence's own editor code serialises it.
Kadence Blocks reads
| Ability | What it does |
|---|---|
wppilot/kadenceblocks-check-setupCheck Kadence Blocks Setup | Reports the presence + version of Kadence Blocks (free) and Kadence Blocks Pro, plus the count of registered blocks per family. This integration is an introspection layer ONLY - it does NOT read or write post_content. To read or write block trees on a post, use the wppilot/gutenberg-* abilities exposed by the base GoBuildWP plugin. Note: Kadence Blocks Pro extends the same kadence/* namespace as the free plugin (unlike GenerateBlocks which uses a separate generateblocks-pro/* namespace). The free/Pro distinction is recovered by inspecting each block's render_callback class - surfaced here as a count per family for at-a-glance sanity checks. |
wppilot/kadenceblocks-get-block-schemaGet Kadence Block Schema | Returns the full attribute schema, nesting constraints, and supports map for a single Kadence-family block. Attributes come straight from WP_Block_Type::$attributes - each key carries type, default, enum when relevant, and any other JSON Schema fields the block author declared. parent / ancestor are nesting constraints. uses_context lists the block-context keys this block reads from ancestors. Pair this with kadenceblocks-list-blocks (catalogue lookup) and wppilot/gutenberg-add-pending-change (write path). |
wppilot/kadenceblocks-list-blocksList Kadence Blocks | Lists every block registered in the kadence/* namespace as a compact catalogue: name, title, family (free/pro), category, is_dynamic, attribute count, plus parent / ancestor nesting hints. Use this to browse the catalogue before calling kadenceblocks-get-block-schema for the full attribute schema of a specific block. Output is intentionally lean (no attribute schemas) - call get-block-schema only on the block you intend to author. |
For the task-level view of Kadence Blocks, with worked requests and what to check afterwards, see Kadence Blocks integration page.