I think Kadence blocks plugin was recently bought or folded in to Liquid Web’s plugins. Ever since, it does not work on local. A new site with only kadence installed or old sites with Kadence basic and/or pro do not work locally, meaning the blocks etc. from these kadence plugins disappear and give the “Failed to load resource” error and
“this block not available” message asking to convert to something else. Never had the issue before. Anyone else experience this? I did contact Liquid; they are mulling it over.
What issue or error are you experiencing?
I think Kadence blocks plugin was recently bought or folded in to Liquid Web’s plugins. Ever since, it does not work on local. A new site with only kadence installed or old sites with Kadence basic and/or pro do not work locally, meaning the blocks etc. from these kadence plugins disappear and give the “this block not available” message asking to convert to something else. Never had the issue before.
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
tried unistalling and reinstalling; tried creating a new site with only kadence plugin active … works fine on dev and prod environments, but once pulled locally, they aren’t available
System Details
Local Version:Version 10.1.1+6939
Operating System (OS) and OS version: 14.3.1 (23D60)
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
Hi @Jerry! Could you share your full Local Log with us?
If you click on the Support tab on the left side of your Local app (Question Mark Symbol), and scroll down a little bit you’ll see a Download Local Log option that generates a zip including all of the relevant logs for us.
Here’s a video showing what’s happening. On all our sites, new and old, when pulled locally, Kadence (free or pro) stops working. We host on WPEngine, where the devs and prods work fine, but on local, Kadence doesn’t work. You’ll see in the video it’s giving “Failed to load resource: the server responded with a status of 400 (Bad Request)” for all kadence blocks. Loom Message - 17 July 2026 | Loom
I’m the only one who work locally here, though we just found another plugin doing the same thing and it’s from the same company, Liquid Web. Both plugins fail to load the css/js locally. A quick run through other plugins we typically use all look fine, just these two.
No, this seems specific to these two plugins. Everything else with local seems fine, though I noticed this only after updating to the most current version, so I thought it might be a glitch. But that timing might have been coincidental. Sites without these plugins all work fine locally; it seems the css/js are not loading on local for these plugins, so checking all the bases. Thxs
Liquid Web responded, saying they can’t duplicate the issue and suspect it stems from the pull from WPEngine to Local. However, this isn’t happening only on sites I recently pulled. Any site I already had in Local that uses Kadence no longer works for the same reason: the css/js from the plugin is not found. ?? I’ve tried deleting the sites and pulling them again, with the same result. I deleted and reinstalled Local, but the result was the same. One error message in console says the CSP is blocking resources, but I don’t have a specific csp on this; is that a default of some kind?
Hi @Jerry - Since you’re the only one who seems to be experiencing the issue have you done any testing to see if it could be related to your device or network? For example can you replicate the same problems if you change your browser or your network? Are you able to test from another device and see if the same thing occurs there?
Hi,
yes, on the office network or my home network, same issues, no matter the browser. Yesterday, I did abandon Local and set up a MAMP environment, and that works fine. I think it’s got to be something with the url referencing from wpengine to Local, though why it only affects two plugins, I don’t know. … I think we can close this and we’ll work around it until some update or other magically fixes it. Thanks for your input
I’m glad to hear you were able to get things working for now @Jerry! If you want to revisit this, or run into more problems down the road, maybe we could gather some information from you in a DM or through WPE support directly so that we could pull or import one of your sites to test. I tried replicating on my end with a bare bones install and just Kadence but couldn’t create the same issue. So trying to replicate with a copy of one your sites might be our next approach.
