Neve fix
Neve Update Broke Your Layout? Check the Theme and Pro Pairing
Yesterday the site was fine. Today the header is taller, the content is narrower and a Pro feature has stopped. After a Neve update the first suspect is not the new version but the pairing: the free theme and the Neve Pro add-on update on separate tracks, and a layout can break simply because one moved and the other stayed.
What you are seeing
- Content width, spacing or fonts changed on every page at once
- The header lost its sticky behavior or a row changed height
- A wp-admin notice says Neve Pro needs a newer version of Neve, or the reverse
- Shop or blog layouts fell back to a plain default
- Pages look right in the Customizer preview and wrong on the live site
Why it happens on Neve
Most common first.
- 1
Neve and Neve Pro updated on different days
The theme comes from WordPress.org and can update itself overnight. The add-on updates through Themeisle, and only with an active license. If one moves a major step and the other does not, the modules that reach into the theme, such as header options, custom layouts and shop layouts, lose their footing.
- 2
A cache is pairing new markup with old styles
Neve generates part of its styling from your Customizer settings, and optimizer plugins merge and minify the result. After an update, a cached page can carry the new HTML with the previous version's CSS. It looks like a broken layout and clears like a stale one.
- 3
The child theme is holding on to old template files
A child theme that copied Neve's template files, or hooks into the theme's internals, was written against the version of the day. When a release reorganizes those files, the child keeps serving its older copy and the two halves of the page no longer match.
- 4
Settings carried over from an earlier format
Neve's header builder and default styling have changed across major releases, and long-running sites carry settings saved the earlier way. The theme converts them on update. Usually that is invisible. Sometimes a row, a width or a button style comes out of the conversion slightly different from how it went in.
- 5
It was not Neve that changed
Automatic updates run in batches. Elementor, a blocks plugin or WooCommerce may have updated the same night, and the theme update was merely the one you noticed. Layouts built in a builder break on the builder's schedule, not the theme's.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Record the versions, then back up
Before changing anything, note the Neve version under Appearance, Themes and the Neve Pro version under Plugins, and read any notice the add-on shows about a required version. Then take a full backup. If your host offers staging, make a copy now and do the remaining steps there.
- 2
Purge the caches and regenerate the CSS
Clear your caching plugin, the host cache and any CDN, then load the site in a private window. If Elementor is in use, its Tools screen has an option to regenerate its CSS files. If the layout comes back, stop there. It was stale CSS, and our fix page on CSS changes not showing explains the layers.
- 3
Put the theme and the add-on on matching releases
Update whichever one is behind. If Neve Pro shows an update it cannot install, the license is the obstacle. Activate it in the Neve dashboard, or download the current add-on from the Themeisle account and upload it under Plugins, Add New, Upload Plugin, where WordPress will offer to replace the installed copy.
- 4
Rule the child theme in or out
On the staging copy, look inside the child theme's folder. A functions.php and a style.css are normal. Copies of Neve's own template files are the suspects, so rename them one at a time and reload. Do not simply activate the parent theme as a test: WordPress keeps Customizer settings per theme and the design will appear to reset.
- 5
Roll back on staging to prove the cause
Neve has offered a rollback link in the theme details panel under Appearance, Themes, with a matching link for Neve Pro beside its entry in Plugins. If yours shows it, roll back on staging. If not, restore the backup there. A layout that returns on the earlier version confirms the update as the cause and gives you a working copy to compare against.
- 6
Compare the two Customizers, then update forward
With the old version on staging and the new one live, open Appearance, Customize on both and walk through Layout, Header, Typography and Buttons. Note what differs and set it again on the new version. Staying on the old release is a pause, not a fix.
Keep it from coming back
- Update Neve and Neve Pro in the same sitting, never one without the other
- Turn off automatic theme updates if nobody looks at the site the next morning
- Keep the child theme to functions and styles, with no copied template files
- Run major releases on a staging copy first and click through the key pages on a phone
The permanent fix
A faster Next.js build, with a CMS made for your business
One broken update is an accident, but a layout that needs rescuing after most updates means the design rests on a theme, an add-on, a child theme and a builder that only hold when all four agree. With Next.js and a custom CMS there is no Neve Pro release to match against the theme. The layout is code that changes when you decide to change it, and the pages are served as static files in the meantime.
| On Neve 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 Neve 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
Yes, as a diagnostic step. Use the rollback link if your install shows one, restore a backup or upload the earlier release by hand, and do it on a staging copy. Roll the theme and the Pro add-on back together. Then find what the new version changed and move forward again, because an old release stops receiving fixes.
Not the same number, but compatible releases. The add-on is built against a recent version of the theme and says so in a wp-admin notice when the pairing is off. The reliable rule is to update both together and never leave one a major release behind.
The Customizer preview is generated fresh for you. Visitors get the cached page, and after an update that page can still carry styles from the previous version. Purge every cache layer and check in a private window before you change a single setting.
No. An update replaces the theme's files, and your settings live in the database. What can change is how a new release reads an old setting, which is why a width or a header row sometimes shifts. Code edited directly inside the theme's files is another matter, and our fix page for a theme that broke after an update covers recovering it.
Keep reading
- 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.
- 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.
- ServiceWebsite Hosting & Maintenance PlansThe watching after launch: managed hosting, tested updates, backups that restore, security and uptime monitoring, and small edits done within a day, month to month.