A theme update replaces the theme’s own files with a newer version, and if any customisation was made directly to those files rather than through a child theme, the update overwrites it without warning — the layout you had disappears the moment the update completes, replaced by whatever the new version’s defaults happen to be.
Before you buy, one quick check
Read-only. Go to Appearance → Themes and see whether a child theme is active, or whether the parent theme itself is the one running directly.
If there’s no child theme, direct customisations were likely overwritten by the update. If a child theme is active and still broke, the cause is more likely a genuine incompatibility between the new parent version and your child theme’s own code, which is a different, more specific problem to trace.
Either answer is useful information to bring when you order, since it changes whether we’re primarily recovering lost work or debugging a real compatibility clash. Checking roughly when the update happened against when the layout actually changed is worth doing too, since the two aren’t always the same moment if a cache delayed the visible effect.
Theme update breaking layout - repair
Your theme's layout changed or broke right after an update. We find whether customisations were lost or there's a genuine incompatibility, and fix it properly.
- 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?
| Layout changed or broke immediately after a theme update, no child theme in use | This fix covers it |
| Layout broke after an update, with a child theme active | This fix covers it, different likely cause |
| The site is completely down, not just visually broken | A site-down diagnosis, different bucket |
| A fatal error appeared, not just a visual layout change | Theme fatal error after core update |
| The update hasn’t happened yet, asking preventatively | Worth discussing setup first; a child theme largely prevents this |
What you are seeing
- Layout, spacing, or design elements that changed immediately after updating the theme
- Custom styling or template changes that simply disappeared
- The site displaying using the theme’s unmodified defaults instead of your customised version
- No fatal error, just a visually different and clearly unintended layout
- The change correlating exactly with the timing of the theme update
Common causes
- Direct edits made to the parent theme’s files instead of a child theme
- Customiser settings reset to defaults by the new version’s updated options
- A child theme referencing template files or functions the parent theme removed or renamed
- CSS specificity or structure changes in the new version overriding previous custom styles
- Cached versions of old CSS or templates conflicting with the newly updated files
What we do
- Identify exactly what changed by comparing the current layout against the last working version
- Determine whether customisations were lost, or a genuine incompatibility is the cause
- Recreate or migrate lost customisations into a proper child theme where that’s the issue
- Resolve any genuine incompatibility between the new parent version and existing customisations
- Clear relevant caches to rule out stale files masking the actual fix
- Confirm the layout matches the intended, working design across the affected pages
What is included
- The cause of the layout change identified and corrected
- Customisations restored or properly migrated into a child theme if that was missing
- Testing across the affected pages to confirm the fix holds
- The pre-fix backup, kept for 30 days
Not included
- Redesigning the site beyond restoring what was there before the update
- Preventing all future theme updates from ever causing this again, beyond proper child theme setup
- Fixing bugs in the theme’s own new version, which is the theme author’s responsibility
- Ongoing monitoring of future theme updates
Questions about this fix
Could I have avoided this?
A child theme protects direct file customisations from being overwritten by updates, so if one wasn't in place, setting one up as part of this fix helps prevent the same thing happening again.
Will I lose the update's own improvements if you fix this?
No — the goal is keeping the new version's improvements while restoring the customisations that were lost, not reverting the update itself.
Why does the Customiser show different settings than before?
Some theme updates change how settings are stored or organised, which can make previously-set options appear reset even though the underlying intent was just to reorganise, not erase, your configuration.
Is it safe to roll back to the previous theme version instead?
It can undo the immediate problem, but it also means missing whatever the update actually fixed or improved, and version history for themes isn't always as accessible as for plugins — we can advise which approach suits your situation better.
Will this happen with every future update once it's fixed?
Not if a proper child theme is now in place for any customisations — that's specifically what protects future updates from repeating this exact problem.
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.