GeneratePress fix
GeneratePress Site Library Import Failed or Stuck? What to Check
The Site Library does four jobs in a row: it installs plugins, sets theme options, imports content and pulls in the images. Each job asks something different of your server, so the place where the import stops tells you most of what went wrong. Before you retry, find out what the first attempt left behind.
- Installing plugins: generateblocks ... done
- Importing theme options ... done
- Importing content: 41 of 118 items
- PHP Fatal error: Maximum execution time of 30 seconds exceeded
- No response from server. Import did not resume.
What you are seeing
- The progress message sits on importing content and never moves
- The Site Library tab is empty or reports that no sites were found
- Required plugins fail to install or activate
- The import finishes and the pages arrive without images or styling
- A second attempt left duplicate pages, menus and widgets
Why it happens on GeneratePress
Most common first.
- 1
The server gives up before the content step ends
Importing content means downloading every demo image and creating every page in one long run. Shared hosting often caps how long a request may take and how much memory it may use, and a proxy in front of the site can cut the connection sooner still. The import does not report the cutoff. It just stops updating.
- 2
The site cannot reach the library
The list of sites and the demo files are fetched from GeneratePress's servers. If the host or a firewall blocks those outbound requests, the library loads empty or the import fails at its first download. An out-of-date GP Premium can have the same effect, because the library it knows how to read has moved on.
- 3
Plugins that cannot be installed
Most library sites need GenerateBlocks, and some need more, such as WooCommerce or a page builder. The importer installs them for you unless the host forbids plugin installs from the dashboard, the file permissions refuse the write or a premium companion needs a license the site does not have.
- 4
A firewall reading the import as an attack
Importing sends large requests full of markup to the server in quick succession. A security plugin or the host's web application firewall can mistake that for an injection attempt and answer with a 403. The importer waits for a reply that was blocked.
- 5
Importing over a site that already has content
The Site Library is built for a fresh install. On a working site it overwrites Customizer settings and adds demo pages, menus and widgets beside your own. A failed first run followed by a retry does it twice.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Protect what is already there
If the site holds any real content or settings, take a full backup before another attempt, or run the import on a staging copy. Then check whether the Site Library offers to remove the previously imported site, and use that to clear the debris of the failed run before starting again.
- 2
See where it stopped and why
Open the browser's developer tools, switch to the Network tab and run the import again. A request ending in 403 points at a firewall, 500 at a PHP error, 504 or a long timeout at server limits. That one status code decides which of the next steps applies.
- 3
Bring GP Premium and the theme current
Update both, then confirm the Site Library module is active under Appearance, GeneratePress. If the library is empty, use its refresh control. If it stays empty, ask the host whether outbound requests to GeneratePress's servers are being blocked.
- 4
Install the required plugins yourself
The import screen lists the plugins a library site needs. Install and activate them from Plugins, Add New Plugin before importing. The importer then has one job fewer, and any license or permission problem shows up on its own.
- 5
Give the content step room
Raise PHP's max_execution_time and memory_limit in the hosting panel, or ask the host to, and pause the security plugin's firewall for the length of the import. If the site sits behind a proxy with a hard timeout, bypass it temporarily. Run the import, then restore every setting you changed.
- 6
Import in two passes
The importer treats theme options and demo content as separate choices. Import the options alone first, which is quick, then the content. If the content still fails, the design settings are in place and you can build the handful of pages you need from the pattern library.
Keep it from coming back
- Import a library site onto a clean install and add your content afterward, never the other way round
- Run imports on staging or during setup, before the domain points at the site
- Remove a failed import completely before retrying
- Once the import is done, delete the demo pages, images and plugins you will not use
The permanent fix
A faster Next.js build, with a CMS made for your business
An import that fails once is a server setting. The larger point is what a successful import gives you: someone else's layout, demo plugins and placeholder pages that the business then edits around for years. If the site has outgrown its starter and each change fights the template, a Next.js build designed from your own content, with a custom CMS shaped to what you publish, starts from the business instead of the demo.
| On GeneratePress 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 GeneratePress 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
You can, and you should not without a backup. The import replaces Customizer settings and adds demo content alongside yours. Use a staging copy, or import the site you like on a blank test install and rebuild the one page you wanted by hand.
The list comes from GeneratePress's servers, so an empty library is nearly always a connection problem or an outdated GP Premium. Update the plugin, refresh the library and ask the host about blocked outbound requests. The license status under Appearance, GeneratePress is worth a look at the same time.
Images are downloaded one by one during the content step, and they are the first casualty when time or memory runs short. The pages exist with empty image slots. Removing the imported site and running it again with higher limits is cleaner than patching the gaps by hand.
Return to the Site Library, which offers to remove the imported site and restore the options that were there before. Check afterward for leftovers: menus, widgets and plugins the demo installed. Anything from a run that crashed halfway may need deleting manually.
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.
- 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.