Salient fix
Salient Demo Import Failed, Stalled or Missing Images? Start Clean
The Salient demo importer does a great deal in one run: hundreds of pages, portfolio items, sliders, menus and images copied onto your server. When it stalls, the cause is usually a missing Salient plugin or a server that gave up before the importer did. Retrying on top of a half-finished import makes things worse, so clean up first.
What you are seeing
- The progress indicator turns for an hour and nothing changes
- Pages arrived, but every image is a gray box or a broken icon
- Rows show up as bracketed shortcode text
- The menu holds every item twice after a second attempt
- The site has the demo's pages and none of its colors or fonts
Why it happens on Salient
Most common first.
- 1
A plugin the demo depends on was inactive
The demo content is written for Salient Core's elements, the Salient builder, Nectar Slider and the portfolio post type. If the plugin that registers one of those is inactive during the import, WordPress skips what it cannot place or stores it as shortcode text. Shop demos expect WooCommerce in the same way.
- 2
The server ended the script early
A full demo is hundreds of items imported in a single long run. Hosts cap how long a script may run and how much memory it may use, and budget plans cap both tightly. The importer gets no chance to report the failure, so the progress indicator just keeps turning.
- 3
The images could not be downloaded
Pages and images arrive separately. The text comes in the import file, and each image is then fetched from the demo server, one request at a time. A host that blocks outbound requests, a firewall or a timeout leaves you with complete pages and an empty Media Library. Some demo photographs may also be swapped for placeholders for licensing reasons, which is by design.
- 4
The import was run a second time
Running the importer again does not resume the first attempt. It adds another copy of everything that succeeded, which is how a menu ends up listing each page twice and the Pages screen fills with duplicates.
- 5
Content arrived without the theme options
The importer handles page content, theme option settings and widgets as separate parts. Pages imported without the options carry the demo's layout and none of its colors, fonts or header, so the result barely resembles the preview you chose.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Use a fresh install or a staging copy
A demo import belongs on an empty site. On a site with real content it scatters hundreds of demo pages, posts and media files among yours. If the site is already live, clone it to staging and import there.
- 2
Remove what the first try left behind
On an empty site, the quickest route is a reset plugin or a fresh WordPress install. On a site with real content, take a backup, then delete the imported pages, portfolio items, sliders, menus and media by hand and empty the trash. Do not import over the remains.
- 3
Activate everything the demo expects
Under Plugins, confirm Salient Core, Salient WPBakery Page Builder, Salient Nectar Slider, Salient Portfolio and Salient Demo Importer are active and current. Add WooCommerce before importing a shop demo.
- 4
Ask the host two questions
What are the PHP time and memory limits on this plan, and can the server make outbound requests to fetch files? If the limits are low, ask for them to be raised for the import. If outbound requests are blocked, the images will never arrive however often you retry.
- 5
Import in parts and leave the tab alone
Open the Demo Importer tab in the Salient options panel and choose the demo. Where the importer lets you pick content, theme options and widgets separately, run the content first and the others after. Keep the tab open until each part reports that it is done.
- 6
Finish the wiring by hand
Under Settings, Reading, choose the demo's home page as the front page. Assign the imported menu under Appearance, Menus, Manage Locations. Visit Settings, Permalinks and click Save Changes. Then open the Media Library and confirm the images landed.
Keep it from coming back
- Import a demo before any real content exists, never after
- Run the importer once, because a second run adds copies and repairs nothing
- Delete the demo pages, sliders and portfolio items you will not use
- Deactivate the Salient Demo Importer plugin once the site is set up
The permanent fix
A faster Next.js build, with a CMS made for your business
The demo has nine sliders and you wanted a home page. A site assembled from an import keeps carrying pages, sliders and plugins it never needed, and if you are importing a demo for the second or third time to get a redesign started, that is worth weighing. On a Next.js build with a custom CMS, every page and every editing screen exists because your business uses it, and nothing arrives that has to be deleted afterward.
| On Salient 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 Salient 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
The images are downloaded from the demo server after the pages are created. If your host blocks outbound requests or the script times out during that stage, the pages exist and the pictures do not. Fix the cause, clear the partial import and run it again from clean.
Not safely. The importer does not pick up where it stopped. It creates a second copy of whatever already came in. Remove the first attempt, then import once with the plugins active and the server limits raised.
It will not delete your pages, but it will bury them. Demo pages, posts, media and menu items are mixed in with yours, and theme options may be replaced with the demo's. Try the demo on a staging copy and rebuild the parts you like on the real site.
WordPress shows recent posts on the front page until told otherwise. Go to Settings, Reading, choose a static page and pick the demo's home page. Then assign the menu to its location, since that link is not always made for you.
Keep reading
- 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.