Enfold fix
Enfold Demo Import Failed or Stuck? What to Check, in Order
You picked a demo in Enfold's theme options, clicked import and watched the progress stop. Or it finished and the site looks nothing like the preview. A demo import is one long request that fetches a package, creates pages and media and overwrites theme options, and it fails at whichever of those your server likes least.
What you are seeing
- The import button spins and never reports success
- An error appears partway and the page count stops growing
- Pages arrive but images, sliders or shop products are missing
- The home page shows your latest posts, not the demo's front page
- A second attempt leaves two copies of every page and menu
Why it happens on Enfold
Most common first.
- 1
The server ends the request before the import does
Importing a demo means creating dozens of pages and media entries in one go. Shared hosting commonly caps how long a PHP request may run and how much memory it may use. When the cap is hit the server ends the request, and the import screen is left waiting for an answer that is not coming.
- 2
The demo's plugins were not active
Each demo lists the plugins it expects, such as WooCommerce for the shop demos or the bundled LayerSlider for some sliders. Import without them and WordPress has nowhere to put products or slider data, so those parts are skipped. The pages that depended on them arrive with holes.
- 3
The demo package could not be downloaded
Recent Enfold versions fetch a demo's files from the author's server at the moment you import, instead of shipping every demo inside the theme. That generally needs a verified token on the Theme Update tab, a host that allows outbound requests and PHP's zip support to unpack the result. Miss one and the import fails before it creates anything.
- 4
An old Enfold importing into a new WordPress
The importer is part of the theme. A copy of Enfold that is years behind runs old import code on a current WordPress and PHP, and notices that were once harmless become fatal errors midway through.
- 5
A previous attempt left half its content behind
The importer adds. It does not clean up first. Each retry stacks more pages, menus and widgets on top of the last partial run, and the result looks like a failed import even when the latest run succeeded.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Start from a backup or a clean install
A demo import overwrites theme options and adds content you cannot remove in one click. Back up the database first. If the site is new, the cleanest route is an empty WordPress install with nothing on it but Enfold.
- 2
Verify the token and update Enfold
Open Enfold, Theme Update, enter your Envato personal token and run the check. Update the theme if a newer version is offered. A current theme with a verified token removes two of the common failures before you begin.
- 3
Activate what the demo asks for
Go to Enfold, Demo Import and read the notes on the demo you want. Install and activate each plugin it names first. Shop demos need WooCommerce with its setup finished, and slider-heavy demos need the bundled LayerSlider enabled.
- 4
Give the request room to finish
Ask your host to raise the PHP execution time and memory limit for the afternoon, or change them in the hosting panel's PHP settings. Tools, Site Health lists the current limits under Info, Server and flags a missing zip module among its recommendations.
- 5
Clear the wreckage before retrying
Delete the pages, portfolio items, media and menus the failed run created, or on a brand-new site reset WordPress with a reset plugin. Then run the import once and leave the tab open until it reports back. Retrying over a partial import only stacks a second set on the first.
- 6
Finish what the import leaves undone
Check Settings, Reading. If the blog list is showing, set the demo's home page as the front page. Confirm the menu is assigned under Appearance, Menus, then save Enfold's theme options once so its stylesheet is rebuilt for this site.
Keep it from coming back
- Import demos on a fresh install or a staging copy, never over real content
- Enter and verify the token before anything else on a new Enfold site
- Run the import once. If it fails, clean up before the second try
- Delete unused demo pages, portfolio items and sliders before launch so Google never indexes them
The permanent fix
A faster Next.js build, with a CMS made for your business
A demo is someone else's site with your logo on it, and much of the work after import is deleting what you did not need. If the import keeps failing, or the result needs so much reshaping that little of the demo survives, the template was never the shortcut it looked like. A Next.js build starts from your own pages and offers, with a custom CMS that holds only the fields your business edits, so there is nothing to import and nothing to clean out.
| On Enfold 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 Enfold 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
Not with a button. The importer adds pages, media, menus and widgets and replaces theme options, and it keeps no record to roll back. On a new site, resetting WordPress and starting over is fastest. On a site with real content, restore the backup you took before importing.
Media is the heaviest part of the import and the part most often cut off by a time limit, so pages can arrive with empty image slots. As with many marketplace themes, some preview images may also be swapped for placeholders for licensing reasons. Either way you will be replacing them with your own.
It should not delete them, but it will change how they look. The import replaces Enfold's theme options, so colors, fonts, header and footer settings switch to the demo's. Your pages stay in the list, now mixed in with the demo's. That is why a live site is the wrong place to try one.
Enfold does not rely on a purchase code screen the way some themes do. It uses an Envato personal token, entered under Enfold, Theme Update, which ties the site to the account that bought the license. Recent versions generally want that token verified before demo files can be downloaded, so set it up first.
Keep reading
- ServiceFixing Broken WebsitesSite down, hacked, or falling apart? We diagnose it fast, fix what's broken, and tell you straight how to keep it from happening again.
- 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.