Theme repair · Neve
Neve Theme Not Working? Start With the Site It Was Imported From
Few Neve sites began as a blank page. Most began as a starter site: a finished demo imported in a few clicks, with a builder, a set of companion plugins and a Customizer full of someone else's decisions. The theme itself is small and steady. Repair starts by separating what you chose from what arrived in the import.
What a Neve site looks like when it needs work
- The phone header is missing the menu, the button or the logo
- Sample pages from the starter site are still published
- The Neve dashboard asks for a license key that was entered once already
- Pro-only touches like the sticky header vanished one morning with no update you remember
- One page has no header at all and nobody remembers switching it off
- An update moved the page width and the spacing around the content
The six places a Neve fault usually hides
Most common first, each with a way to check it yourself.
- 1
A starter site that was never fully made yours
Neve's starter sites arrive through a companion plugin from Themeisle, which installs the plugins the demo needs, imports its pages and overwrites the Customizer. When the run stalls, or finishes and nobody tidies up, the site keeps demo pages, a second set of menus and plugins that exist only because a template asked for them.
Check it: Open Plugins and ask of each one whether you chose it or the import did. Then look in Appearance, Menus for a menu you never built.
- 2
Two header layouts, one of them unattended
Neve's header builder lives in the Customizer and keeps a desktop arrangement and a mobile arrangement side by side. They share components but not placement. A button dropped into the desktop row does not exist on a phone until someone places it there, and the slide-out mobile menu has to be given contents of its own.
Check it: Go to Customize, Header, switch the builder to its mobile view and tap the menu icon in the preview. An empty panel is your answer.
- 3
The theme and the Pro add-on drifted apart
The free theme updates from WordPress.org whenever a release lands. Neve Pro is a separate plugin that updates only while its license is active. When the key lapses, or was never activated on this address, the theme moves on and the add-on stays where it was. The features that span both are where the cracks show.
Check it: Compare the Neve version under Appearance, Themes with the Neve Pro version under Plugins. A notice from the add-on about a required theme version settles it.
- 4
A license that belongs to someone who left
Neve Pro is licensed through a Themeisle account, and each key allows a set number of sites. On handed-over sites the account often belongs to the freelancer or agency that built it. Their staging copies hold the activations, their card pays the renewal and you find out when either stops.
Check it: Ask who can sign in to the Themeisle account that owns the key. If the answer takes more than a minute, the license is not really yours.
- 5
Settings split between the Customizer and the page
Neve sets container width, sidebar and header globally in the Customizer, then lets each page override them from its own settings panel in the editor, including switches that hide the header, the title or the footer. Add a builder template such as Elementor Canvas and a single page can take orders from three places.
Check it: Open the odd page in the editor and read its Neve settings panel, reached from the Neve icon in the editor's top bar. Any switch that is on explains itself.
- 6
A child theme that moved your settings out of sight
WordPress stores Customizer choices per theme, so Neve and a Neve child theme each keep their own set. Activate a child theme after the design is finished and the header, colors and layout appear to reset. Nothing was deleted. The settings are sitting under the parent's name.
Check it: Under Appearance, Themes, note whether a child theme is active and when it was switched on. A design that vanished the same day was left behind, not lost.
The Neve problems we fix most
Each has its own page: what you are seeing, why, and the fix in order.
- Starter Site Import FailedThe importer stopped partway and left half a demo behind. Find the step that failed and rerun it cleanly.See the fix for Starter Site Import Failed
- Header Builder IssuesA row is missing, the phone menu is empty or Publish does nothing. Three Neve header faults, sorted.See the fix for Header Builder Issues
- Neve Pro License Not ActivatingThe key is rejected or the Pro modules went missing. Check the plugin, the key and the site count, in that order.See the fix for Neve Pro License Not Activating
- Update Broke the LayoutNeve updated and the page shifted. Check the theme and add-on pairing, the cache and the child theme before rolling back.See the fix for Update Broke the Layout
Do this today
Sign in to wp-admin and write down three things: the Neve version, the Neve Pro version and the name on the Themeisle account that holds the license. If you cannot find the third, start there. A site whose add-on cannot update is a site waiting for its next surprise.
How we work through a Neve site
- 1
Trace what the import brought
We list every page, menu, widget and plugin and mark which came from the starter site, which you added and which nothing uses. That inventory tells us what can be removed without anyone noticing.
- 2
Pair the versions and the license
Neve, Neve Pro and the starter-sites plugin are checked against each other. The license is traced to the Themeisle account that owns it and its activations are counted.
- 3
Copy the site, then change it
Header rebuilds, module changes and updates happen on a staging copy with a backup behind it. The live site carries on taking calls.
- 4
Check it on a phone before it goes live
Each template is opened on a real phone and on a desktop, the menu is tapped and the forms are sent. Only then does the work move across.
What you get back from a Neve repair
The starter site's leftovers removed
Demo pages, placeholder images, duplicate menus and import-only plugins taken out, so what remains is the site you actually run.
A header and footer built for both layouts
Desktop and mobile arrangements set deliberately, the mobile menu filled, and any page-level switch or builder template that hides them accounted for.
A license the business controls
The Neve Pro key moved to a Themeisle account you control, stale activations released and the add-on brought level with the theme.
The site's settings written down
A short record of which Customizer sections, Pro modules and page overrides shape the site, so the next person does not have to rediscover them.
Repair it, or start over?
The honest answer depends on the site, not on what we would rather sell.
Repair it when
- The site is Neve plus one builder, and the faults trace to an import, a header or a license
- The pages still say what the business does and the design has not dated
- Somebody on your side edits it happily when it behaves
- The Neve Pro license can be renewed or moved into an account you own
Rebuild it when
- The site is still mostly the starter demo with your logo on it
- Elementor templates, Pro custom layouts and page overrides all decide the same header
- Each round of updates needs a rescue, and the rescues are getting closer together
- Neve Pro, the starter-site plugin and the theme each need watching, and you would rather have static pages on Next.js with an editor shaped around what you actually change
The permanent fix
A faster Next.js build, with a CMS made for your business
When a Neve site spends more time being repaired than being used, the stack is the problem, not the last update. A Next.js build replaces the theme, the builder and the plugins with one codebase made for this site, and a CMS that shows your team only what they actually change.
| 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.
When to bring someone in
Call before you run a second starter-site import over a live site, because the importer replaces Customizer settings and adds content beside what is already there. Call when Pro features have gone and the license sits in a former contractor's account, since that needs a handover as much as a fix. And call when the same layout fault returns after every update. Something is being patched that should be settled.
Tell us where your Neve site came apart
Describe what you see and what changed last. We will check the starter import, the header builder, the Pro add-on and the license, then tell you which one is responsible.
Which of these sounds like you? (pick any)
Frequently asked
Neve is light, actively developed by Themeisle and seldom the direct cause. The trouble usually comes from what surrounds it: a starter site nobody finished customizing, a Pro add-on out of step with the theme or a builder with its own ideas about the header. Find which of those it is before blaming the theme.
Neve Pro is an add-on plugin that switches on extra modules. Depending on the plan, those include more header builder options, custom layouts, blog and WooCommerce extras and premium starter sites. If you use none of them, the free theme is enough. If you use any, the license needs to stay active so the add-on keeps pace with the theme.
Some of them. A starter site installs whatever its demo pages were built with, often a blocks or builder plugin, a forms plugin and the importer itself. The importer can go once you have finished importing. The others should be checked page by page on a staging copy, because a blocks plugin removed too early leaves broken blocks where its content used to be.
Both work. Neve was built to sit under either, and its starter sites come in versions for each. What causes trouble is mixing them without a rule: some pages in Elementor, some in blocks, a header from one and a footer from the other. Pick one tool for page layouts and let Neve's builder own the header and footer.
Repair it if the design still fits and the faults are specific: an import, a header, a license. Consider a rebuild when the site is still the demo underneath, when several tools decide the same thing or when every update costs you a day. At that point a Next.js build with a custom CMS takes the theme, the add-on and the plugin stack out of the picture, and what you edit is only your own content.
A mobile header or a license handover is often settled soon after we have access. Cleaning up after a half-finished starter import takes longer, because every demo page and plugin has to be judged before it is removed. You get a time estimate after the first look, not before.
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.
- ServiceBest WordPress DesignA WordPress site that looks the part and does the work. Custom design, fast pages, and a layout built to turn visitors into customers.
- ServiceReplacing WordPressWhen WordPress becomes the thing you fight instead of the thing that works, it's time to move. We migrate you without losing rankings.
- Hub · WordPress Repair Hub
- Page · Moving from WordPress to Next.js
- WordPress repair · Astra Theme Problems: How to Fix a Site That Stopped Behaving
- WordPress repair · Kadence Blocks Errors or a Broken Header? Fix Your Kadence Site
- WordPress repair · Why Your Elementor Site Got Slow, Fragile and Hard to Edit
- Fix · WordPress Theme Broke After an Update
- Fix · CSS Changes Not Showing on the Website
- Fix · Elementor Not Loading or Not Saving
- Fix · WordPress Memory Exhausted Error
- Guide · WordPress vs. Next.js: The Technical Difference, in Plain Words
- Guide · WordPress vs. a Custom Website: The Business Decision