Key facts at a glance
GeneratePress troubleshooting in 2026
Last updated
- Elements need Display Rules or they show nothing
- Every Block, Hook, and Layout Element requires at least one Include location set under its Display Rules tab. An Element with no location configured never appears on the site, no matter how it is set up.
- GP Premium modules are opt-in, not automatic
- Installing and activating GP Premium is only the first step. Each module, Colors, Typography, Spacing, WooCommerce, Hooks, and more, must be individually enabled under Appearance then GeneratePress. A feature that looks missing is usually a module that was never switched on.
- Site Library imports have server requirements
- A Site Library import needs PHP memory of 256M, an execution time of 300 seconds, and a post max size of 512M per the GeneratePress documentation. Below these, the import stalls or returns a 500 error partway through.
- Many Site Library templates require GenerateBlocks
- GenerateBlocks is a separate free plugin. Templates in the Site Library built with GenerateBlocks blocks need the plugin installed before the import, or the layout blocks on the imported pages render empty. GenerateBlocks is not the same as GP Premium.
- License not connected means no updates
- The GP Premium license key must be entered in the Updates box under Appearance then GeneratePress. Without it, WordPress cannot reach the GeneratePress update server and update notifications never appear in the dashboard.
- Four distinct products, one ecosystem
- GeneratePress, GP Premium, GenerateBlocks, and GenerateBlocks Pro are separate products with separate licenses. Problems often come from a missing dependency between them, not a fault in any one product.
Source: the GeneratePress documentation on the Elements system, Site Library imports, error codes, and pricing, the GeneratePress and GenerateBlocks pages on WordPress.org, and our hands-on GeneratePress repairs. Get a quote in 60 seconds →
Why GeneratePress sites break
GeneratePress is one of the lightest and best-coded themes on WordPress.org, with over 500,000 active installations, and the theme core is almost never the cause of a problem. What breaks are the subsystems that surround it. GeneratePress is unusually modular compared to most themes, and that modularity is what makes it fast and flexible, but it also means that a feature which looks missing is almost always a module that has not been switched on, a Display Rules condition that was not set, or a dependency between products that was not installed.
The GeneratePress ecosystem is made up of distinct products that must be understood as separate things. The free GeneratePress theme is the base. GP Premium is a separate modular plugin that adds the Elements system, the Site Library, and other capabilities to the theme, but only after each module is individually enabled. GenerateBlocks is a separate free plugin that extends the block editor, built by the same author, and works with any theme. GenerateBlocks Pro extends the blocks plugin further. These are separate products with separate installations and separate licenses, and mixing them up is a common source of support confusion.
Generic theme problems such as a white screen after an update, PHP 8 fatals, or a conflict with another plugin are not GeneratePress-specific and are covered on our WordPress theme repair hub and our plugin repair hub. This page stays on the subsystems that are specifically GeneratePress: the Elements system and Display Rules, the GP Premium module activation step, the Site Library importer, and the license and update connection.
Where GeneratePress problems come from
Nearly every GeneratePress-specific problem is one of these four. Naming yours points straight at the fix.
The Elements system and Display Rules
An Element is not showing, is showing in the wrong place, or two Elements are colliding in the same location. Display Rules are the governing logic that says where each Element appears, and every one of these symptoms is a Display Rules configuration problem rather than a bug. An Element with no location set shows nowhere. An Element with an overly broad Include condition shows everywhere. Two Elements with overlapping conditions and no Exclude rules between them both fire in the same spot. A Hook Element with Execute PHP enabled and a syntax error throws a fatal on every page it targets.
A GP Premium feature or module is missing
GP Premium is installed but a setting or panel is nowhere to be found in the dashboard. This is almost always the module activation step. GP Premium modules are not enabled by default. After installing and activating the GP Premium plugin, you still need to go to Appearance then GeneratePress and switch on each module you want. Until that step is done, the module and its settings are simply absent from the dashboard, which makes it look like a missing feature when it is actually an unactivated module.
The Site Library import stalls or produces incomplete results
The import hangs, returns a 500 error, or finishes but leaves images missing or layout blocks empty. A stalled or failed import is almost always a server resource limit. An import that finishes but produces empty blocks is almost always a missing GenerateBlocks plugin on a template built with GenerateBlocks. Both have specific fixes that are distinct from the other, and knowing which one you have points at the right solution.
GP Premium license not connected or updates missing
GP Premium is installed and working, but updates are not appearing in the WordPress updates screen. This is almost always the license key, which must be entered in the Updates box under Appearance then GeneratePress, and which is easy to overlook because there is no forced setup wizard after installing the plugin. Without a connected license, the site has no channel to the GeneratePress update server. For generic white screens or PHP breaks after an update, the fix lives on the theme hub.
Error and symptom reference
Find the exact GeneratePress symptom you see. Each row says what it means and how it is fixed.
| Error or symptom | What it means and how to fix it |
|---|---|
| An Element is published and enabled but does not appear anywhere on the site | No Display Rules location is set on the Element. Every Element needs at least one Include location under its Display Rules tab. Open the Element, add a location, and publish. |
| An Element is appearing on pages where it should not show | The Include conditions in Display Rules are too broad, or a required Exclude condition is missing. Narrow the Include rules to the specific pages or post types you intend, or add the unwanted locations as Exclude conditions. |
| Two Elements are stacking or colliding in the same location | Two Elements share the same hook location with overlapping Display Rules and no Exclude conditions separating them. Add Exclude conditions to one Element so the two do not fire at the same location on the same pages. |
| A PHP fatal error on every page the Hook Element targets | Execute PHP is enabled in a Hook Element and the PHP code has a syntax error. Disable Execute PHP or narrow the Display Rules to a test page to stop the fatal, then fix the PHP syntax before re-enabling. |
| A GP Premium module feature is not appearing in the dashboard after installing GP Premium | The module has not been enabled. GP Premium modules are opt-in. Go to Appearance then GeneratePress and enable each module you need from that panel. Installing the plugin alone is not enough. |
| The Appearance then GeneratePress panel is missing entirely | The GP Premium plugin is installed but not activated. Go to Plugins, find GP Premium in the list, and activate it. The panel only appears once the plugin is active. |
| Site Library import hangs on Importing or returns a 500 error | A server resource limit is cutting the import short. Raise PHP memory to 256M, max_execution_time and max_input_time to 300, and post_max_size to 512M. Check current values under Tools then Site Health then Server. |
| Site Library import completes but images are missing or layout blocks are empty | A partial import from a timeout, or the template requires the GenerateBlocks plugin which was not installed before importing. Install GenerateBlocks, confirm server settings, and retry the import. |
| GP Premium license key will not activate | A leading or trailing space in the pasted key is the most common cause. Paste carefully without extra spaces into the Updates box under Appearance then GeneratePress. Confirm the license is active in your generatepress.com account. |
| GP Premium updates are not showing in the WordPress updates screen | The license key is not entered in the Updates box under Appearance then GeneratePress, or was pasted with an extra space. Without an active license, WordPress cannot reach the GeneratePress update server. |
| White screen or critical error after a GeneratePress update | A PHP fatal from a conflict or old code, not a GeneratePress bug. Switch to a default theme or rename the GeneratePress folder to recover, then read the debug log for the exact fatal. |
| GeneratePress or GenerateBlocks fights another plugin and the editor or layout breaks | A plugin conflict. Use Troubleshooting Mode in the Health Check plugin to isolate the conflicting plugin for your session only, without affecting visitors. |
What we fix
Twelve problem areas cover almost every GeneratePress emergency. We diagnose which one is actually yours rather than guessing.
Element Not Showing Anywhere
An Element is published but never appears. Always a missing Display Rules location. We check the Display Rules tab, set the correct Include conditions, and confirm the Element is enabled.
Element Appearing on Wrong Pages
Display Rules are too broad or missing an Exclude condition. We narrow the Include rules to the exact locations you intend and add the Exclude conditions that prevent it from appearing elsewhere.
Two Elements Colliding in One Location
Two Elements share the same hook with overlapping Display Rules and no exclusion between them. We add the correct Exclude conditions so each Element fires only where it should.
Hook Element PHP Fatal
Execute PHP is on in a Hook Element and the code has a syntax error, firing a fatal on every page the Element targets. We stop the fatal, fix the syntax, and scope the Display Rules to prevent recurrence.
GP Premium Module Missing
A GP Premium feature is not appearing because the module was never enabled under Appearance then GeneratePress. We activate the plugin and enable the right modules from that panel.
Appearance then GeneratePress Panel Missing
The GP Premium plugin is installed but not activated as a plugin. We activate it so the panel appears, then walk through module activation for the features you need.
Site Library Import Hanging or 500 Error
A server resource limit is cutting the import short. We identify the limiting setting and raise the PHP memory, execution time, and post max size to the values the import needs.
Partial Import or Empty Blocks After Import
The import finished but images or blocks are empty, often because GenerateBlocks was not installed first. We install GenerateBlocks, confirm server settings, and re-run the import cleanly.
GP Premium License Will Not Activate
A pasted key with a trailing space, or a connectivity issue reaching the GeneratePress license server. We paste the key cleanly into the Updates panel and confirm the connection.
GP Premium Updates Not Showing
The license key is not entered in the Updates panel under Appearance then GeneratePress. Without it, WordPress cannot receive update notifications from the GeneratePress server.
GeneratePress vs Plugin or Builder Conflict
GeneratePress or GenerateBlocks fights another plugin and the editor or a layout breaks. We isolate the conflict using Troubleshooting Mode and resolve it without disabling what you need.
GenerateBlocks Not Installed for a Site Library Template
A Site Library template built with GenerateBlocks produces empty blocks after import. We install the free GenerateBlocks plugin and re-run the import so the template renders correctly.
The Elements system and Display Rules
The Elements system is GeneratePress Premium’s signature feature and the source of its most common support questions. Elements are reusable pieces of content or layout that you build in the WordPress block editor and then place anywhere on your site by selecting a location in the Display Rules. There are three main element types, each serving a different purpose.
Block Elements
Block Elements let you build content using the WordPress block editor, then insert that content at a location you specify via Display Rules. Common uses are author boxes, call-to-action sections, top bars, and footer bars. The Display Rules on a Block Element control whether it appears on the entire site, specific post types, individual pages, or certain categories. You can also add Exclude conditions to prevent it from showing on specific pages even if the Include conditions would otherwise match them.
Hook Elements
Hook Elements fire a Block Element at a specific WordPress action hook inside GeneratePress, such as before or after the content, inside the site header, or at any of the hooks GeneratePress exposes. This is useful for injecting content at precise points in the page structure without editing template files. Hook Elements have an Execute PHP toggle that runs PHP code through the hook. When that toggle is on and the PHP code has a syntax error, the fatal fires on every page the Display Rules target. Keep Execute PHP off unless PHP code is genuinely needed, and always test it with Display Rules scoped to a single page before broadening the rules.
Layout Elements
Layout Elements let you change the sidebar layout and content width settings for specific pages or post types rather than applying one global setting to the whole site. For example, you can use a Layout Element to remove the sidebar on all category archives while keeping it on single posts, or to set a wider content area on landing pages. Layout Elements follow the same Display Rules system as Block Elements.
Include conditions say where the Element fires. Exclude conditions say where it does not, even if the Include conditions would otherwise match. An Element set to Entire Site as the Include condition shows on every page of the site, including the homepage, archives, and posts. If you want it only on posts, set Include to Singular then Post, not Entire Site. If you want it on all posts except one specific post, set Include to Singular then Post, and add that one post as an Exclude. When two Elements share the same hook and overlapping Include conditions, both fire in that location at the same time. The fix is to add Exclude conditions to one Element for the pages where the other should show instead.
Site Library import failures
The Site Library is a GP Premium module that gives you access to professionally designed starter sites you can import with one click. It is the fastest way to get a GeneratePress site from blank to fully designed, but it is also the most resource-intensive job a modest hosting plan will run, and it is where most GeneratePress support questions originate.
When you trigger a Site Library import, the process connects to the GeneratePress servers, installs any required plugins including GenerateBlocks if the template needs it, then downloads and processes all the content, images, and design settings. Each step requires PHP memory, execution time, and a stable connection. Below the required thresholds, the import stalls partway through or returns a server error.
| Server setting | What GeneratePress recommends |
|---|---|
| PHP memory limit | 256M recommended for a complete Site Library import. Below this, the import stalls or returns a 500 error partway through content processing. |
| Max execution time | 300 seconds. A shorter server default kills the import process before it finishes downloading all content and media from the GeneratePress servers. |
| Max input time | 300 seconds. Controls how long the server accepts incoming data during the import sequence before timing out. |
| Max upload file size | 256M so media files and plugin packages can be transferred during the import without hitting the upload size ceiling. |
| PHP post max size | 512M. Must exceed the upload file size limit, or large import payloads are rejected before they reach PHP processing. |
| GenerateBlocks plugin | Required for many Site Library templates. Templates built with GenerateBlocks blocks need the free plugin installed before importing, or the block areas render empty. |
Check your current values under Tools then Site Health then the Server section, which lists the PHP memory limit, execution time, upload size, and post max size. If they fall below the recommended values and your host panel lets you edit php.ini or .htaccess, raise them there. If you cannot change them directly, ask your hosting provider to raise them, as many hosts set defaults well below what the plan actually allows.
A partial import that completes without a visible error but leaves layout blocks empty on the imported pages is almost always a missing GenerateBlocks plugin. Many templates in the Site Library are built with GenerateBlocks blocks. If the GenerateBlocks plugin is not installed before the import, the blocks are present in the imported content but have no plugin to render them, so they appear empty or invisible on the front end. Install the free GenerateBlocks plugin from Plugins then Add New, then retry the Site Library import for the same template.
The GeneratePress documentation also notes that ModSecurity on the server can block the data transfer between your site and the GeneratePress import servers, producing partial or failed imports. If you have ruled out server resource limits and the import still fails, ask your hosting provider to temporarily disable ModSecurity while you run the import, then re-enable it afterward.
GP Premium license and updates
GP Premium is sold as an annual subscription at generatepress.com. The license covers up to 500 sites per subscription, including client sites you build and manage. After purchase, your license key is available in your generatepress.com account.
Where to enter the license key
The license key is entered under Appearance then GeneratePress in your WordPress dashboard. On that page, look for a box labeled Updates on the right side of the Elements list. Paste the key from your generatepress.com account into that box without any leading or trailing spaces, then save. A confirmation message appears once the license is active. After activation, update notifications from GeneratePress.com begin reaching your site through the standard WordPress updates screen.
Why updates stop appearing
If GP Premium updates are not showing in the WordPress updates screen, the license key is almost always the answer. Without an active license connected in the Updates panel, the site has no channel to the GeneratePress update server and update notifications never appear. A key pasted with a space at either end also prevents activation. Each site where you want to receive updates needs the license key entered separately in the same panel. Confirm the subscription is also active and not expired in your generatepress.com account.
Single license on multiple sites
A GP Premium license covers up to 500 websites per the generatepress.com licensing terms, including client sites where you build, develop, and manage the site. You enter the same license key on each site through its own Appearance then GeneratePress panel. The restriction is that the license cannot be shared with third parties or used to install GeneratePress for someone without ongoing management. The GenerateBlocks Pro license follows a similar system and must be managed separately.
Why specialist GeneratePress work helps
The difficulty with GeneratePress problems is that the symptom rarely maps obviously to the cause, and the product ecosystem creates multiple places to look. An Element not showing looks like a theme bug but is always a Display Rules configuration. A missing premium feature looks like a billing problem but is almost always a module that was never switched on. An import failure looks like a broken theme but is a server resource limit or a missing plugin. An absent update looks like a licensing failure but is an unconnected key in a panel most owners never notice.
We work on GeneratePress sites regularly, so the process is the same every time. Identify which of the four products is involved and which subsystem is the cause. For an Element problem, read the Display Rules on each affected Element and look for missing Include conditions or absent Exclude conditions. For a missing module, check the Appearance then GeneratePress panel and toggle the right module on. For a Site Library failure, read the Site Health server settings against the documented requirements and raise the limits before retrying. For a license or update problem, paste the key cleanly into the Updates panel and confirm the subscription in the account. We charge a flat rate because we are fast at getting to the right layer.
The 2-hour guarantee and the money-back promise are the enforcement. And when the real answer is that the hosting plan does not provide the resources the Site Library import needs, we say so plainly rather than charging to fight a limit only the host can raise.
Related fixes and hubs
GeneratePress problems often sit next to a broader WordPress issue or a plugin conflict. These are the pages for the ones that reach past GeneratePress itself.
White screen or theme install errorThe theme repair hub, the parent of this page. White screen after any theme update, install errors, PHP 8 breaks, child themes, and the Customizer.
Theme repair hub →GeneratePress fights another pluginThe full conflict isolation method. When GeneratePress or GenerateBlocks and another plugin collide, this is how you find the pair without visitor downtime.
The conflict-finding method →Site broke after a PHP 8 upgradeA GeneratePress theme or plugin version using deprecated PHP code throws a fatal after a host moves to PHP 8. Revert to get online, then update or patch.
Fix a PHP version break →Running Astra insteadThe sibling per-theme spoke for the Astra ecosystem. Starter Templates import failures, Astra Pro licensing, and the Header Footer Builder.
Astra repair hub →Running Kadence insteadThe sibling per-theme spoke for the Kadence ecosystem. Block validation errors, Kadence Blocks Pro dependencies, and Kadence Theme Kit Pro.
Kadence repair hub →Everything WordPress repairThe parent hub for plugin, theme, update, and critical-error repairs across WordPress, with GeneratePress as one part of it.
Visit the WordPress hub →Pricing and process
Send your site and the symptom
Use the quote form with your URL and what happened: an Element not showing, a GP Premium module missing, a Site Library import hanging, or a license not activating. A senior engineer replies with a flat-rate quote, usually within 30 minutes during business hours.
Approve, we start immediately
No scheduling step, no kickoff call. Approve the quote and we begin. You provide WordPress and hosting access through a secure link. The clock starts on the 2-hour guarantee.
Fixed and confirmed
We fix the real cause, whether that is Display Rules, a module, server resources, a missing plugin, or a license, confirm the GeneratePress feature works, and tell you what happened. Money back if we cannot fix it for the agreed scope.
GeneratePress FAQ
My GeneratePress Element is not showing anywhere on the site. Why?
An Element with no Display Rules location set never appears, because GeneratePress does not guess where you want it. Every Element needs at least one Include location entered under its Display Rules tab before it shows anywhere on the site. If you added the Element, published it, and see nothing, open the Element, go to the Display Rules tab, and confirm that a location is selected, for example the whole site, a specific post type, or a particular page. An Element set to Enabled but with no Display Rules location applied is the most common reason for an Element that simply does not appear.
My GeneratePress Element is appearing on pages where it should not show. How do I fix it?
Display Rules that are too broad, or missing Exclude conditions, are almost always the reason an Element appears where it should not. If you set an Element to show on the Entire Site but only wanted it on a specific post type, it shows everywhere. Go to the Display Rules tab for that Element and either narrow the Include conditions to the specific pages, post types, or categories you intend, or add the pages where you do not want it as Exclude conditions. When two Elements target the same hook location with overlapping Display Rules and no exclusion between them, both fire at the same location and produce a doubled or colliding output. Adding Exclude conditions to one Element so the two do not fire at the same location on the same pages resolves the collision.
A Hook Element with PHP code is causing a fatal error on my site. What do I do?
The Execute PHP toggle in a Hook Element runs your PHP code through the hook you selected, so a PHP syntax error in that code throws a fatal error. Because the Element has Display Rules, the fatal fires on every page those rules target, which can take the site down if the Display Rules are set broadly. The first step is to disable the Execute PHP toggle on the Element, or set its Display Rules to a single test page only, to stop the fatal on the live site without deleting the Element. Then fix the PHP syntax error in an external editor before re-enabling the toggle. Hook Elements run in the context of the hook they target, so the code also needs to avoid naming conflicts with functions already defined by the theme or other plugins. Once the PHP is clean and tested, re-enable Execute PHP and restore the original Display Rules.
I installed GP Premium but the module feature I need is not showing anywhere. What am I missing?
The most common reason a GP Premium feature is missing is that the module for it has not been enabled. GP Premium is a modular plugin. After you install and activate the GP Premium plugin in WordPress, you still need to go to Appearance then GeneratePress and enable each module you want from that panel, for example Colors, Typography, Spacing, Secondary Navigation, WooCommerce, or the Hooks module. Until a module is enabled from that screen, its settings and features do not appear anywhere in the dashboard. This is the module activation step that is easy to miss: installing and activating GP Premium is not enough on its own, each module must be switched on separately from the Appearance then GeneratePress panel.
The Site Library import is hanging on Importing or returns a 500 error. Why?
A Site Library import that stalls or returns a 500 error is almost always a server resource limit, not a bug in GeneratePress. The import connects to the GeneratePress servers, installs any required plugins including GenerateBlocks if the template needs it, then downloads and processes all the content and media in sequence. Each of those steps uses PHP memory and execution time, so a hosting plan with tight defaults cuts the process short. The values the GeneratePress documentation names for a Site Library import are a PHP memory limit of 256M, an execution time of 300 seconds, a max input time of 300 seconds, a max upload file size of 256M, and a post max size of 512M. Check your current values under Tools then Site Health then Server and raise whichever fall below those thresholds. If you cannot change them yourself, ask your host to raise the PHP memory limit and execution time for the import.
A Site Library template imported but the images are missing or the blocks are empty. What now?
A partial import where the process completed but images or content did not fully transfer usually comes from a timeout or a server resource limit that cut the import short before all assets were pulled. Many templates in the Site Library are also built with GenerateBlocks blocks, so importing one of those templates without the GenerateBlocks plugin installed means the layout blocks exist but render nothing. Install GenerateBlocks from the Plugins menu, then retry the import. Also confirm that ModSecurity is not enabled on the server during the import, as it can block the data transfer from the GeneratePress servers and produce partial results. The GeneratePress documentation notes that you can ask your hosting provider to disable ModSecurity while you use the Site Library and re-enable it afterward.
How do I activate my GP Premium license key, and why are updates not showing?
The GP Premium license key is entered under Appearance then GeneratePress in your WordPress dashboard, where you will find a box labeled Updates on the right side of the page. Paste the key from your generatepress.com account into that box and save. When the license activates, a confirmation message appears above the Elements area, and update notifications from the GeneratePress server begin reaching your site. If updates are not showing in the WordPress updates screen, the most common reason is that the license key has not been entered in that Updates panel, or the key was pasted with a leading or trailing space. Without an active license connected in that panel, your site has no way to contact the GeneratePress update server, so update notifications simply do not appear. Each site where you want to receive updates needs the license key entered in the same way.
What is the difference between GeneratePress, GP Premium, GenerateBlocks, and GenerateBlocks Pro?
They are four distinct products with four separate purposes and licenses, all by the same author. GeneratePress is the free WordPress theme on WordPress.org with over 500,000 active installs. GP Premium, which stands for GeneratePress Premium, is a separate plugin that adds modules to the free theme: the Elements system including Hook, Block, and Layout Elements with Display Rules, the Site Library, Styling Controls, Secondary Navigation, WooCommerce controls, Off-Canvas Panel, and Sticky Navigation, each enabled individually under Appearance then GeneratePress. GenerateBlocks is a separate free WordPress.org plugin with over 200,000 active installs that extends the block editor with advanced layout and query blocks, and it works with any theme, not just GeneratePress. GenerateBlocks Pro is a premium extension of the GenerateBlocks plugin that adds Global Styles, a pattern library, animations, and additional dynamic tags. A site can run the free GeneratePress theme without any of the others, or combine the whole suite depending on what the design requires.
Do I need GenerateBlocks to use GeneratePress?
GenerateBlocks is not required to use the GeneratePress theme or GP Premium. The free GeneratePress theme works on its own, and GP Premium modules work on the theme without GenerateBlocks. GenerateBlocks is a separate free plugin that adds block-editor layout capabilities, and many GeneratePress sites never install it. The place where GenerateBlocks becomes important is the Site Library: many templates in the Site Library are built with GenerateBlocks blocks, so importing one of those templates without GenerateBlocks installed means the layout blocks are present in the import but render nothing on the front end. If you are trying to import a Site Library template and the result looks wrong or empty, installing the free GenerateBlocks plugin is often the missing step.
How fast can you fix a GeneratePress problem, and what does it cost?
Most GeneratePress problems resolve inside the 2-hour window because they fall into a small set of known causes. A Display Rules conflict is a configuration fix once you identify exactly which Include and Exclude conditions are set on each affected Element. A missing GP Premium feature is a module activation step under Appearance then GeneratePress that takes minutes once you know the step exists. A Site Library import failure is a server resource fix at the hosting level. A license not showing updates is a key-entry fix in the Updates panel. An Execute PHP fatal is a syntax fix combined with a scoped Display Rules change to prevent future recurrence. Pricing is a flat 49 to 149 dollars with no hourly billing, and the money-back guarantee applies if we cannot fix the agreed problem. When the honest answer is that a server resource limit needs raising at the hosting level, we say so plainly rather than charging to fight a limit only the host can raise.
Sources and further reading
The GeneratePress-specific facts on this page come from the official GeneratePress documentation and the GeneratePress and GenerateBlocks pages on WordPress.org.