Block patterns and template parts are pre-built arrangements of blocks meant to be reused consistently across a site, and when the pattern’s own saved structure becomes inconsistent with what the blocks inside it currently expect — often after a theme or plugin update changes one of those blocks — every page using that pattern can display incorrectly at once, even though nothing about those individual pages was ever directly edited. That’s exactly what makes this kind of fault confusing to diagnose without knowing where to look — the natural instinct is to check the page that’s misbehaving, when the actual problem lives one level up, in the shared pattern itself.
Open the Patterns panel to see what’s actually affected
Read-only. Open the Patterns section of the Site Editor and check whether the pattern itself shows a warning there, versus the issue only appearing on specific pages that use it.
A warning on the pattern itself points at a more fundamental structural problem than an issue isolated to how one page happens to be using it.
Checking a second or third page that uses the same pattern is also worth doing, since a fault confined to genuinely one page points somewhere different than one affecting every instance identically.
Block pattern & template part repair
A block pattern or template part isn't displaying correctly, or won't save. We identify what's broken in the underlying pattern and repair it.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A block pattern or template part displays incorrectly or won’t save | This fix covers it |
| A Full Site Editing template itself is the one throwing an error | Full Site Editing template errors, a related but distinct fix |
| A single custom block, not a pattern, shows a validation error | Custom block validation errors, a different fix |
| You want unused, cluttered patterns cleaned up, not a broken one repaired | Reusable block & pattern cleanup, a different service |
| The block editor itself won’t load for any content | Block editor not loading – diagnosis, a different fix |
What you are seeing
- A pattern or template part displaying incorrectly across every page that uses it
- A warning shown specifically on the pattern in the Site Editor’s Patterns section
- The pattern failing to save changes correctly when edited
- The issue appearing after a theme or plugin update
- Individual pages using the pattern otherwise functioning normally around it
Common causes
- A synced pattern edited from one instance in a way that changed the saved pattern itself, not just that one page
- A pattern imported from another site or a pattern library, built around a block this site doesn’t have registered
- The editor silently upgrading an older pattern’s format on save, in a way one of its own blocks doesn’t recognise
- A pattern nested inside another pattern, where the inner one changed independently of the outer one still referencing it
- Corrupted markup from an interrupted save while editing the pattern directly in the Patterns panel
What we do
- Open the pattern in the Site Editor’s Patterns panel and confirm exactly what’s inconsistent in its saved markup
- Check whether it’s a synced or unsynced pattern, since that changes how a fix actually propagates
- Repair the pattern’s block structure to match what its components currently expect
- Re-save and confirm every page using the pattern picks up the corrected version
- If the pattern is nested inside others, confirm those still reference it correctly
- Check the Patterns panel for any other pattern carrying the same latent structural issue
What is included
- The specific pattern or template part issue identified and repaired
- Verification across every page using the affected pattern
- A check for the same issue in other patterns
- The pre-fix backup, kept for 30 days
Not included
- Redesigning the pattern beyond restoring it to a valid, working state
- Fixing a third-party block plugin’s own underlying bugs
- Cleaning up unused or cluttered patterns, which is a separate service
- Ongoing monitoring for future theme or plugin updates affecting patterns
Questions about this fix
Can a pattern break for everyone even if only one person edits it?
Yes, if it's synced — a synced pattern has one saved copy shared everywhere it's used, so an edit from any single page updates the source everyone else sees too.
Is an unsynced pattern safer than a synced one?
Safer from this specific failure, since an unsynced copy can't be broken by an edit made elsewhere — the tradeoff is that you lose the ability to update every instance from one place, which is usually why synced was chosen initially.
Is a synced pattern more likely to have this problem than a regular one?
Synced patterns propagate changes across every instance automatically, which is powerful but does mean a bad edit can spread the same way a good one would, making this issue somewhat more visible when it happens.
Could a plugin I haven't touched recently really cause this?
Yes, if that plugin provides a block used inside the pattern and its own update changes how that block is structured, patterns using it can be affected without anything about the pattern itself being edited.
Does this affect the block editor itself, or just how the pattern renders?
Just the pattern's rendering — the block editor keeps working normally for everything else, since the issue is isolated to this one pattern's own saved structure.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.