Kadence fix
Kadence Blocks: 'This Block Contains Unexpected or Invalid Content'
The warning means the editor rebuilt the block from its settings, compared the result with the markup saved in your page and found a difference. Visitors still get the saved version, so nothing is broken yet. What happens next depends on which button you press.
- Block validation: Expected attributes (2), instead saw (3).
- Block validation failed for `kadence/column`
- Content generated by `save` function:
- <div class="wp-block-kadence-column kadence-column214_3f2a">
- Content retrieved from post body:
- <div class="wp-block-kadence-column ..." data-aos="fade-up">
What you are seeing
- A gray box replaces the block, with an Attempt Recovery button
- The live page looks normal while the editor shows warnings
- The same warning appears on every page that uses one pattern
- Blocks went invalid right after a plugin update or a rollback
- Only pages last saved by one user are affected
Why it happens on Kadence
Most common first.
- 1
The plugin's saved format moved and the content did not
Each Kadence block has a save routine that produces its markup. When a release changes that output, the plugin ships a record of the old format so earlier content still validates. If that record does not cover your block's exact settings, or Kadence Blocks was rolled back to a version older than the content, the editor no longer recognizes what it finds.
- 2
Kadence Blocks Pro was deactivated
Pro adds options to the free blocks, such as scroll animations and dynamic content, and those options leave traces in the saved markup. With Pro inactive, the free plugin regenerates the block without them. The comparison then fails on every block that used a Pro option.
- 3
The page was saved by a user who cannot post raw HTML
WordPress filters markup saved by roles that lack the unfiltered HTML capability, such as Authors and Contributors, and everyone below super admin on a multisite network. Inline SVG and certain attributes inside block markup are stripped on save. The page looks fine until it is reopened, and then each filtered block is flagged.
- 4
Something edited the markup outside the editor
A database search-and-replace during a migration, a bulk edit plugin or a hand edit in the code view changes the saved HTML without touching the block's settings, or the reverse. The two halves of the block no longer describe the same thing.
- 5
The block lives in a synced pattern
A synced pattern is stored once and displayed wherever it is used. One invalid block inside it raises the warning on every page that includes the pattern, which makes a single fault look like a site-wide collapse.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Leave the recovery button alone on the live page
Take a backup, then copy the page to a staging site or duplicate it as a draft. Recovery rewrites the block the moment you save, and on a live page the revision history is your only undo.
- 2
Bring the Kadence plugins level
In Plugins, update Kadence Blocks to the current release and make sure Kadence Blocks Pro is active if the page was built with it. Reload the editor. Warnings caused by a missing Pro option, or by a release that has since been corrected, often clear with no recovery at all.
- 3
Read what the editor objects to
Open the browser's developer tools on the Console tab and reload the editor. Each invalid block logs a validation message that sets the markup the save routine produced beside the markup found in the post. The difference is frequently one attribute or one class, and it names the cause.
- 4
Use Resolve to compare before choosing
Open the three-dot menu on the warning and choose Resolve. WordPress shows the current markup next to the converted result. Convert to Blocks rebuilds from the stored settings. Convert to HTML keeps the old markup as a Custom HTML block, and since Kadence generates each block's CSS from its settings, that frozen copy can lose its styling on the front end.
- 5
Recover one block and check it against the public page
Press the recovery button on a single block, then compare it with the live page side by side: column widths, padding, backgrounds, icons, link targets and mobile settings. Most Kadence settings are stored apart from the markup and usually survive. Anything the editor had to read from the markup itself, such as text it could not parse, is what can go missing.
- 6
Fix the source, then work through the rest
For a synced pattern, repair the pattern once and every page that uses it follows. For a permissions cause, have an administrator open and re-save the affected pages. Then recover the remaining blocks page by page, updating each only after you have checked it.
Keep it from coming back
- Update Kadence Blocks and Kadence Blocks Pro together, on staging first
- Never roll Kadence Blocks back without restoring content from the same date
- Keep Pro active for as long as any page uses a Pro option
- After a migration, open key pages in the editor before calling it done
The permanent fix
A faster Next.js build, with a CMS made for your business
An invalid block is a disagreement between two descriptions of the same thing, and the block editor stores both in every post. If warnings return after each round of updates, the content is bound too tightly to one plugin's markup. A custom CMS stores content as plain fields and the Next.js templates render them, so a design change never has to rewrite what your team wrote.
| On Kadence today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Kadence site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
It discards the saved markup for that block and writes fresh markup from the block's stored settings, using the plugin version now installed. Settings held in the block's attributes carry through. Anything the editor had to read out of the old markup and could not parse is replaced with a default or left empty. Nothing is final until you click Update.
No. The warning exists only in the editor. The front end keeps serving the markup saved in the post, which is why a page can look perfect in public and alarming in wp-admin. The exposure comes later, when someone opens the page, clicks through the warnings and saves without checking.
They are separate faults. Invalid content means the block's plugin is active but its output no longer matches the saved markup. The unsupported message means the plugin that registers the block is not running at all, usually because Kadence Blocks or Kadence Blocks Pro was deactivated. Reactivating the plugin fixes the second without any recovery.
Not safely from the editor, which validates blocks one page at a time. A developer can script a bulk pass, but each block type still needs its result checked. The practical order is to fix the cause first, repair shared patterns next and then work through pages by traffic, since the rest still display correctly in the meantime.
Keep reading
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.
- ServiceDesign & Layout FixesOverlapping text and broken spacing tell a customer you do not sweat details. We fix the glitches so the site looks as competent as the business.
- ServiceCMS DevelopmentGive your team a cleaner way to publish. We build content systems with clear templates, safe editing fields, reusable blocks, and SEO structure that survives the next update.