OceanWP fix
OceanWP Demo Import Failed? Clear the Half-Import and Retry
An OceanWP demo arrives in several deliveries: required plugins, sample pages, images, Customizer settings, widgets and forms. Ocean Extra's importer asks your server to accept all of it in a single run, and budget hosting often hangs up halfway. The fix is rarely to press the button again. It is to find which delivery failed and bring in the rest piece by piece.
What you are seeing
- The import window sits on one step and never reports success
- An error appears partway through, or the screen simply times out
- Pages exist but their images are gray placeholders
- Colors, fonts and the header do not match the demo preview
- A second attempt left two of every page and menu item
Why it happens on OceanWP
Most common first.
- 1
The host cut the request short
Importing the sample content means creating dozens of pages and downloading every image from OceanWP's demo server inside one request. Shared hosting commonly ends a request well before that finishes. The importer stops where it was cut off and says very little about it.
- 2
A required plugin was missing or inactive
Each demo names the plugins it was built with, typically Elementor, a forms plugin and sometimes WooCommerce. Skip one and its content arrives as empty sections or raw shortcodes, because nothing on the site knows how to draw it.
- 3
A pro demo without a live license
The premium demos need the Ocean Pro Demos extension and often other paid extensions besides. With the license lapsed or those plugins absent, the demo either refuses to import or imports with holes where the paid features were.
- 4
The host blocked the image downloads
The pages travel as text in a file. The images are fetched one at a time from a remote server. A host firewall that limits outbound requests, or a time limit that expires mid-download, leaves the pages in place and the Media Library full of placeholders.
- 5
The import ran twice, or over a live site
The importer adds. It does not replace. Run it again and you get a second set of pages, a second menu and widgets stacked on widgets. Run it on a site with real content and the demo's Customizer settings write over your own.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Decide what kind of site this is
On a new, empty install you can retry freely. On a site with real pages, stop, take a full backup and export your Customizer settings from the Theme Panel. A demo's Customizer file replaces your colors, fonts and header choices.
- 2
Read the demo's requirements list
Open the demo again from the Install Demos screen in the Theme Panel and note the plugins it asks for. Install and activate each one, and bring OceanWP and Ocean Extra to their current versions. For a pro demo, confirm the license is active and the paid extensions are installed.
- 3
Remove what the failed run left behind
On a fresh site, the cleanest route is a WordPress reset plugin and a new start. On a live site, delete the sample pages, posts, menus and media the failed run created, sorting by date, so the next attempt does not duplicate them.
- 4
Import in parts, content first
The importer lets you choose what to bring in: the content, the Customizer settings, the widgets and the forms. Tick only the content and run it. When that completes, run the Customizer settings alone, then the widgets. Small requests finish where one large request would not.
- 5
Give the server more room
If the content step still stalls, raise PHP's maximum execution time and memory limit in the hosting panel, or ask the host to raise them for the afternoon. This import is likely the heaviest single job the site will ever run.
- 6
Do the jobs the importer skips
Choose the imported home page under Settings, Reading. Assign the menu to the Main location under Appearance, Menus. Re-save Settings, Permalinks, then regenerate Elementor's CSS from Elementor, Tools so the imported pages pick up their styles.
Keep it from coming back
- Import demos onto a fresh install or a staging copy, never over live pages
- Install and activate every required plugin before you start
- Run the import in parts, and delete a failed run before retrying
- Replace sample pages and images promptly, so demo leftovers never go live
The permanent fix
A faster Next.js build, with a CMS made for your business
A demo is a shortcut to someone else's design, and a site built on one keeps its origins: sample pages, a plugin list chosen for the demo and settings nobody on your team picked. The demo looked finished because somebody else finished it. If you have imported twice and still spend your days deleting things, a Next.js build with a custom CMS may be the shorter road, with each page designed for its own content and an editor that contains only your fields.
| On OceanWP 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 OceanWP 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
Usually because the server ended the request before the content and images finished loading. The importer does everything in one long run, and shared hosting limits how long a single request may take. Importing in parts, content first, gets most stalled demos through.
The importer downloads each image from OceanWP's demo server during the content step. If the request timed out or the host blocked the downloads, the pages arrive and the pictures do not. Delete the failed run's content, raise the time limit and import the content again. You will be replacing most of those images with your own in any case.
You can, and it is the riskiest way to do it. Sample pages and menus are added beside yours, and the demo's Customizer settings overwrite your colors, fonts and header. If you only want one layout, import the demo on a staging copy and carry that page across as an Elementor template.
Only on a site with nothing worth keeping. A reset wipes posts, pages and settings, which suits a fresh install and would be a disaster on a live one. On a site with real content, remove the failed import's pages, menus and media by hand, then import the parts that are missing.
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.
- 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.
- WordPress repair · Why Your Elementor Site Got Slow, Fragile and Hard to Edit
- WordPress repair · Astra Theme Problems: How to Fix a Site That Stopped Behaving
- Page · Moving from WordPress to Next.js
- Fix · 504 Gateway Timeout Error
- Fix · WordPress Memory Exhausted Error
- Fix · Elementor Not Loading or Not Saving