-
Hi there
I’ve been troubleshooting a persistent issue with my setup and would like your help verifying if my GeneratePress installation might be corrupted.
Here’s a detailed summary of everything I’ve checked and the current situation:
Main site (client): https://inessanjose.com
Custom Cloud Library: https://bocetos.eduardosans.com
Theme: GeneratePress Premium
Page builder: GenerateBlocks Pro
Hosting: standard WordPress installation (no custom server rules)
🧪 Troubleshooting steps already performed
Disabled all plugins except GenerateBlocks and GenerateBlocks Pro.
→ Problem persisted.Switched to the default Twenty Twenty‑Four theme.
→ Problem persisted.Disabled security plugins (Wordfence, CookieYes).
→ No effect.Reconnected the GeneratePress license and Cloud Library.
→ The Cloud started working again after reconnection.Reinstalled WordPress core completely from Dashboard → Updates → Reinstall now.
→ No change.Reinstalled GenerateBlocks Pro from my account.
→ No change.Checked all CSP and X‑Frame‑Options headers.
→ No restrictive headers present.Tested on multiple browsers and incognito modes.
→ Same behavior.Activated debugging mode (WP_DEBUG = true)
→ No PHP errors or warnings displayed.Checked custom child theme files (functions.php and style.css).
→ Valid code, no syntax errors.Later I noticed that GeneratePress itself could not be re‑activated — after clicking Activate, it simply reloads the page without enabling the theme. That makes me suspect the main theme files might be corrupted.
💥 Current behavior
My custom templates from the Cloud Library now appear in the editor, but
⚠️ the CSS classes are not applied when inserting them into pages.
The layout and styling break completely, as if the block classes were stripped.The same Cloud Library works perfectly on other websites, so the issue is specific to inessanjose.com.
GeneratePress seems partially broken — I can’t activate it normally, and it doesn’t output its expected structure in the backend.
I enclose a video testing a couple of things:
https://www.loom.com/share/b84fa5f3bbfe46d5a5acc556f5304793💡 What I suspect
There may be a corruption or mismatch between GeneratePress core files and how GenerateBlocks Pro handles Cloud template imports on this particular installation (bocetos.eduardosans.com).
It looks like the block attributes (classes and styling) are not being registered or rendered correctly when the patterns are inserted.🙏 What I need
Could you please:
Verify if this issue could stem from a corrupted GeneratePress installation?
Confirm if there’s a known problem where imported Cloud templates lose their CSS classes?
Perform a clean reinstallation procedure that keeps my GeneratePress Premium settings intact?
Thank you very much for your time — I provide temporary access if you need to inspect the installation directly.
-
Hi there,
Do you have any backups or a staging version of your custom Cloud Library site? We may need to troubleshoot it directly, but doing so on the live site could be risky as it might cause something to break.
-
Very true Alvind, I just made a staging site of that same site with the library cloud and updated the info for its access.
Thanks
-
Hi there,
I tried connecting to your source site’s pattern library on my testing site, and every pattern is working properly.
Here are the screenshots:
https://app.screencast.com/I8df0k0K5e626
https://app.screencast.com/RG4eGJfbnRY4F
https://app.screencast.com/Ykc1XtvreS9Ts
https://app.screencast.com/wZhYHqnFYpGdWSo your source site does not have any issue; the issue is coming from the testing site where you load the library.
Can you disable all plugins on the testing site except GP Premium, GB, GB Pro and GB Cloud? And switch to the parent theme as well?
Let me know how it goes!
-
Hi Ying
This is potentially affecting +40 sites, all of them working with gp premium, generateblocks and cloud. I tried in 6 different sites and all of them present the same issue. These pages have been working with libraries for at least a year with no problem whatsoever, and all of the sudden all of them have the same issue.
The bundle I gave you access to is a testing site, with no content whatsoever. I disabled all plugins, revert to the parent theme and the issue still persists. You can check yourself and see.
My suspicion? I don’t know, the only thing I added lately to the library was a collection of 4 navigation menus and 1 mega menu. Could that be the issue?
It is a real mess, because now all my clients can access my libraries when they shouldn’t. Please guys find a solution. Thanks.
-
Hi Eduardo,
I don’t think the newly added patterns are causing the issue, there doesn’t seem to be any direct correlation.
I did some testing on your bundle site: I removed all the existing remote library connections that were previously linked to your main pattern library host and reconnected them to the staging site (cliente2) library. Surprisingly, the patterns now load correctly on the bundle site.
I can’t really tell what caused the issue, since both the main and staging pattern sites are identical (assuming you cloned the main site to create the staging version). To investigate further, could you try generating a new pattern key on the main site and test if connecting with that new key resolves the issue?
-
Well, first things first. It is a first step that we get to make it functional in at least a site. That’s great :). And yes, I just cloned the site which makes things even more awkward.
So I tried creating a new key in the main hosting site and when uploading the new key onto the bundle, an error triggered saying “unable to get library name”. This never happened before.
It really feels like the whole key system might be corrupted somehow in the main pattern library host. The issue is that I’m using those keys for all my clients, so it would be great if we could find a solution that wouldn’t force me to go client after client enabling/disabling again these libraries.
I am updating the accesses to grant you access to the main hosting site as well, in case you want to check or test anything (do not worry, I have daily backups, I can always revert)… because it feels like something is corrupted in that specific site and it would be great if we could just fix it.
Thanks in advance
-
I’ve disabled all other plugins except GP, GB, and GC on the main hosting site for testing (hope that’s okay). After that, I reconnected the pattern from the main site to the bundle site — and it’s now loading the correct pattern.
Can you check your other sites that are connected to the main site’s pattern library and see if they’re also loading the correct patterns now? At this point, it seems like the issue was a connection error between the main hosting site and the connected sites.
-
Great job! now it works !! 🙂 thanks a lot.
Should I enable back the plugins on the main hosting site? what do you think happened? because it is very weird.
-
Now you can enable the plugins back one at a time, after activating each plugin, check if the connection is still there to find out which plugin is causing the issue.
-
I have to be honest, I’m a little confused as to what has happened. I’ve enabled all plugins, one by one, purging the caché (on both the host and the bundle), reloading the libraries and so on, and it just works fine now. I cannot replicate the error.
I’m super happy it is working but I’m still wondering why it failed. Anyway, I’m closing the ticket :).
Thanks!
-
You are welcome 🙂
- You must be logged in to reply to this topic.