-
Based on your description, all block plugins stop working, right?
When all blocks disappear or fail to load, it almost always means: Some JavaScript or REST API request is intermittently failing.
Can you provide the admin login again?
-
I am sending it privately.
Thank you
-
The login is incorrect. I got locked out, might not be able to log in for a while.
Please check the credentials.
-
Hello, both the username and password are working.
-
I tested editing both the homepage and a single post, and from what I can see, the issue only occurs with the Greenshift blocks. You can see this in the screen recordings below:
Home: https://cln.sh/HFVTkLnFN0s0QWKTfrZF
Single Post: https://cln.sh/6nTkJ6gMBTfVBJTmQSzGThe error probably started on the day when I:
➡️ Uploaded your PHP code to update GP one.
➡️ Installed the Flyingpress plugin (I deleted it on the same day)
➡️ Uploaded a local font to the website using your instructions.I dont think the PHP for Secandary API is causing that issue, but you can temporary remove that snippet now and see if that have some relation to it.
Also, instead of using the old method to add local font, you should use the Font Library module instead since you alredy have GP Premium.
-
Let’s say so. But how is it possible that errors appear on most pages even where I don’t use greenshift at all? + In the videos I sent, you can see that Generateblocks often does not work.
Local Font Library – But I can’t download the font with latin-ext there, or am I mistaken? I’m from the Czech Republic.
Thank you
-
I am not able to see the editor; it does not render at all, just white as you video shows.
I have disabled all plugins, it’s still the same.
So it’s obviously not a GB or GP Premium issue.
You do not have other themes installed, can you install WP’s twenty twenty five theme to test?
-
My server (shared hosting) is getting overwhelmed by dozens of simultaneous requests.
Sends hundreds of requests to the server. Specifically, it is this request:
GET /wp-json/generateblocks/v1/dynamic-tag-replacements?_locale=user
For example
“2026-02-18T13:12:52.761Z” “POST” “/wp-json/generateblocks/v1/dynamic-tag-replacements” “9374ms”
“2026-02-18T13:12:52.757Z” “POST” “/wp-json/generateblocks/v1/dynamic-tag-replacements” “8767ms”The maximum time often reaches 22 seconds.
It seems that GenerateBlocks is indeed responsible for this.
-
However disable GB plugin doesn’t help, so there should be other issues.
And the more dynamic tags you have on the site, the more requests it will send, this is expected.
Please check with your host or go to dashboard > tools > site health > info > server to see if your server setup can meet these basic requirements.
1. PHP max input variables 4000
2. PHP time limit (max_input_time) 1200
3. PHP memory limit 512M
4. Max input time 600
5. Upload max filesize 300M
6. PHP post max size 512M -
Well, I’m sure that no standard shared hosting provider in the Czech Republic (or most of Europe) allows a PHP time limit of 1200 seconds – that’s 20 minutes for a single script, which is excessive for a live web environment.
I have checked my Site Health and here is my current setup:
PHP Memory Limit: 512M (Matches your requirement)
Max Input Variables: 10000 (Exceeds your 4000 requirement)
Max Execution Time: 300s (I increased this to the hosting maximum)
Post Max Size: 256M
The issue is clearly not the server capacity, but the frequency and duration of REST API requests to the dynamic-tag-replacements endpoint. Each request takes about 9.3 seconds. When the editor fires dozens of these at once, it exhausts the available PHP workers (25) of the shared hosting, causing a 504 timeout.
The website is relatively small, so I don’t know where the performance is being lost. It doesn’t make sense to me, but the server debug log doesn’t lie.
-
Each request takes about 9.3 seconds.
That is abnormal, as the request should not take so long. Normal healthy responses for this endpoint should be in the range of 50–800 ms (often under 300 ms on decent hosting), even when processing multiple dynamic tags.
Here are the typical culprits:
1. Too many dynamic tags on the current page/block
– Complex pages with dozens (or 100+) dynamic tags (especially in Query Loops, repeated Containers, Headlines, etc.) cause the endpoint to do a lot of expensive processing per request.
– In older versions or misconfigured sites this can balloon easily.2. Slow / expensive dynamic tag sources
– Custom dynamic tags (via filters) that run slow PHP code
– ACF / Metabox / user meta / options fields that involve database queries, transients that expired, or external API calls.
– Third-party plugins that hook into GB’s dynamic tag or similar and do heavy work3. Query Loops with high post-per-page in editor
– If you have Query Loops set to show 20–50+ posts and those posts use dynamic tags → the preview fetches and processes everything → massive slowdown
– GenerateBlocks docs even have a specific article about this: setting posts per page to -1 temporarily in editor + a filter to limit preview items.4. Server/hosting bottlenecks
– Very low PHP workers / timeout settings.
– Shared hosting with resource limits (CPU / I/O throttling)
– Database on a slow remote server or huge unoptimized tables (wp_postmeta especially)However, it does not look like your site has 1,2,3 issues, that’s why I suspect it’s related to your server. But based on the homepage layout, it only has 2 query blocks with low posts per page, I don’t think they requires lots of resources.
Something else on the site is consuming excessive resources and contributing to GB’s requests being delayed.
Can you provide the admin login again?
-
Hello, thank you, I will send it in a private message.
Hopefully, the Wordfance plugin will let you in.
If you would rather have a copy of the website via WP Staging, please let us know.
-
Thank you for the credential. If you can make a staging site for us to do the testing, that will be great!
-
Done
Otherwise, as I said, this error often occurs on various pages, not just the homepage. Sometimes everything works normally.
-
I have disabled all other plugins and re-installed GB and GB Pro on your staging site, it seems to have solved the issue, can you check?
https://app.screencast.com/mRMSyW07LwrO4
https://app.screencast.com/ivP6v2C2A7nSo
- You must be logged in to reply to this topic.