Kadence patterns ability reference
Reference for the GoBuildWP Pro 1.12.4 source. Installed schemas and policy remain authoritative.
This Kadence patterns ability reference covers listing the patterns in Kadence Blocks' Design Library and inserting one into a block-editor post. The module is separate from Kadence Blocks, which only reads block schemas, and from the Kadence theme module, which edits theme settings.
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 patterns needs before these load
Kadence Blocks must be active; the module is gated on it. Listing needs no Kadence account, and inserting needs the edit_posts capability plus permission to edit the target post.
- Kadence patterns editions
- free, pro
Where the patterns come from
Local patterns are block patterns registered by the theme or plugins, plus the site's saved patterns, that use Kadence blocks. Cloud patterns are the sections of Kadence's Design Library, fetched from Kadence's pattern server. Kadence's own editor sends the site's domain, and for its paid libraries the licence key and email, with those requests; this module sends none of them. The index and each pattern's markup are cached for 12 hours, and if the library cannot be reached the list falls back to the copy Kadence's editor cached, and says so.
Patterns marked as needing a Kadence licence are hidden by default and cannot be inserted from here; on 29 September 2026, 524 of the library's 878 sections were in that group. Inserting those still works through Kadence's Design Library inside the block editor. Patterns that bring their own posts, such as Kadence forms, are refused too, because only Kadence's inserter creates those.
What an insert guarantees
The pattern goes in at the start, the end, or after a numbered top-level block, and every existing block is kept byte for byte: the content is split on block delimiters rather than re-serialised. Kadence scopes each block's CSS by a uniqueID, so any ID the post already uses is renamed throughout the inserted copy. Posts laid out by Elementor, Beaver Builder, Divi, Bricks, WPBakery, Oxygen or Breakdance are refused, as is classic-editor content.
After saving, the post must parse to its old block count plus the pattern's. For a published post the page is also loaded as a visitor: every inserted uniqueID has to appear in it, with Kadence's generated CSS present. Images stay on Kadence's server and are listed as remote_images, so they can be imported to the media library if the site should host them. The insert is undone with wppilot/rollback-change, which restores post_content only.
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 testimonial section to the end of an existing landing page built with Kadence blocks.
- 01
wppilot/kadence-list-patternsSearches the library for testimonials; licensed patterns are left out unless asked for. A listed pattern can still be refused at insert, for example one that brings its own posts, such as a Kadence form. - 02
wppilot/kadence-insert-patternInserts the chosen pattern at the end of the page, renames clashing uniqueIDs and, on a published page, checks the rendered result as a visitor. - 03
wppilot/rollback-changeOnly if the section is wrong: puts the page's previous content back.
Kadence patterns reads
| Ability | What it does |
|---|---|
wppilot/kadence-list-patternsList Kadence Patterns | Lists Kadence Blocks patterns this site can insert without a Kadence account. "local": block patterns registered by the theme or plugins, and the site's saved patterns (wp_block), that use Kadence blocks. "cloud": Kadence's Design Library sections with their categories, fetched from Kadence's library without the site's domain or licence and cached for 12 hours; patterns marked requires_licence cannot be inserted by wppilot/kadence-insert-pattern, and it also refuses patterns that bring their own posts (Kadence forms). When the library cannot be reached, falls back to the copy Kadence's editor cached, if any, and says so. Filter by category or search; page with limit and offset. |
Kadence patterns writes
| Ability | What it does |
|---|---|
wppilot/kadence-insert-patternInsert Kadence Pattern | Inserts one Kadence pattern's block markup into a block-editor post at the start, the end, or after a top-level block (after_index, 0-based, counting top-level blocks only). Existing blocks are kept byte for byte. Refuses posts laid out by a page builder (Elementor, Beaver Builder, Divi, Bricks, WPBakery, Oxygen, Breakdance), classic-editor content, licensed cloud patterns and patterns that bring their own posts (Kadence forms). Kadence uniqueIDs the post already uses are renamed so each block keeps its own CSS. Checks that the saved content parses to the expected block count and, for a published post, loads the page as a visitor and checks that every block rendered and Kadence generated its CSS. Pattern images stay on Kadence's server; remote_images lists them. Undo with wppilot/rollback-change, which restores only post_content. |