Porto fix
Porto Demo Import Failed or Stuck? How to Rerun It Cleanly
A Porto demo is hundreds of posts, images, widgets and sliders plus a full set of theme options, fetched from Porto's server and written into yours in one sitting. When the import stalls, something along that route gave out: the license check, the companion plugin or the server's patience. The half-imported site in front of you is recoverable, and what you do on the next run decides how cleanly.
- Demo: Shop 12 (Elementor) · package downloaded
- Plugins: Porto Functionality, WooCommerce active
- Importing dummy content: 218 of 604 items
- Import request to admin-ajax.php failed: 504 timeout
- Widgets: not started
- Theme options: not started
What you are seeing
- The import progress bar stops and never moves again
- The Setup Wizard spins on its plugins step or its demo step
- Pages arrived but the home page is blank or unstyled
- Menus, widgets or sample products appear twice
- The demo list is locked and asks you to activate the theme
Why it happens on Porto
Most common first.
- 1
The server ran out of time before the importer did
Importing demo content is long, heavy work for PHP, and budget hosting caps how long a request may run and how much memory it may use. Porto's Setup Wizard lists those limits on its status step before you choose a demo. A row flagged there predicts exactly this failure.
- 2
The theme is not registered on this domain
Porto's demo library opens only after the purchase code is registered. A code already registered to a staging address, an old domain or a developer's test install counts as in use, and the importer stays locked or fails when it asks Porto's server for the demo package.
- 3
Porto Functionality is missing, inactive or older than the theme
Demo content is made of Porto's own elements, post types and builder templates, and all of those live in the Porto Functionality plugin. Import without it, or with a release behind the theme, and WordPress receives content it has no way to file. The run stops or finishes with holes.
- 4
The demo was built for a page builder you did not install
Each Porto demo comes in a version for a particular builder. Choose the Elementor version with only WPBakery active, or the reverse, and the pages arrive as empty shells or as raw shortcodes. The import technically succeeded. The site just cannot read it.
- 5
A second run stacked on the first
After a stall, the natural move is to click Import again. Each attempt adds whatever it manages to bring in, so the site collects duplicate menus, repeated pages and widgets in triplicate, and the home page setting may point at the wrong copy.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Stop clicking Import and take stock
Every extra run adds another layer to sort out. If the site held real content before the import, back up the database now. If it is a fresh install with nothing to lose, note that starting clean will be your cheapest option.
- 2
Read the status step of the Setup Wizard
Open Porto, Setup Wizard and look at the server status list: memory limit, execution time, input variables and upload size. Raise anything flagged in your hosting panel's PHP settings, or ask the host to, before another attempt.
- 3
Confirm registration and the required plugins
On Porto's dashboard screen, check that the purchase code is registered to this exact domain. Then open Plugins and confirm that Porto Functionality is active and current, along with the builder your chosen demo version was made for.
- 4
Clear out the partial import
On a new site, wipe it back to empty: reset the database with a reset plugin or reinstall WordPress, then activate Porto again. On a site with real content, delete only the demo's pages, menus, widgets and sample products by hand, and empty the trash so slugs are free for the rerun.
- 5
Import in pieces, content first
Porto's importer lets you choose what to bring in, such as content, widgets and theme options. Run content alone, then the rest. If the standard run still times out and your version offers an alternative import mode, use it. It is slower and far more tolerant of a modest server.
- 6
Finish by hand what the import skipped
Point Settings, Reading at the right home page and attach the menus under Appearance, Menus. Then open Porto, Theme Options and save once so Porto recompiles its stylesheets. A home page that arrives unstyled after an apparently clean import is usually waiting on that save.
Keep it from coming back
- Run the import on a fresh install or a staging copy, never over live content
- Clear every flagged row on the wizard's status step before choosing a demo
- Import the demo closest to your real site. The one with nine sliders looks effortless because someone else is hosting it
- Delete the sample pages, products and sliders you will not use before launch
The permanent fix
A faster Next.js build, with a CMS made for your business
If this is the third attempt to make a demo fit a business it was not designed for, the importer is not the real problem. A demo hands you someone else's page structure and a stack of plugins to keep in step from the first day. There is no setup wizard on Next.js: your pages and products are moved in once, served as static files and edited in a custom CMS, because there is no demo to import.
| On Porto 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 Porto 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, but not on top of the first attempt. Remove the partial content before you rerun, or the site ends up with two of everything and a menu that points at the wrong half. On a brand new install, resetting to empty is faster than sorting duplicates.
A standard ThemeForest license covers one site, and Porto records the domain a code is registered to. If the code was used on a staging copy, an old domain or a developer's test install, deactivate it from the Porto dashboard there first. If that install is gone, Porto's support can usually release the code, or a second license settles it.
It adds pages and does not delete yours. The risk is everything around them: the import can replace theme options, widgets, menus and the home page assignment, which changes how your existing pages look. That is the reason to run it on a staging copy when the site already has content.
Usually four small things. The home page is not set under Settings, Reading. The menus are not assigned to Porto's menu locations. The theme options were skipped or have not been compiled into stylesheets yet. And some demo photographs may arrive as placeholders, because the originals are licensed images the theme cannot redistribute.
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.
- 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.