[Resolved] Updating failed. The response is not a valid JSON response.

[Randy]

Thanks Tom, that link you provided did the trick. The rule has to be set for /wp-json/wp/v2/gblocks_global_style , /wp-json/wp/v2/gp_elements , and /wp-json/wp/v2/gblocks_templates so far…let me know if you think there are others (pages, posts and other element types update fine)

So…for others that may see this: this was not an issue with GP / GB and wordpress 5.7 but just a coincidence of timing with cloudflare firewall rules.

[Tom]

I assume that Cloudflare has added core post types to the rule by default. This is likely something that needs to be done for any custom post type using the block editor. The ones you mentioned cover the GP/GB custom post types.

Yea – just a coincidence here. Glad it’s all sorted now 🙂

[Randy]

Thanks for the great help and guidance on this Tom!

[Tom]

No problem!

[Steven]

Hi guys,
I am not sure if I am allowed to piggyback on this thread but it was the best one I found on this topic.

For anybody having issues I ended up whitelisting my IP address in my firewall settings and that did the trick.

Thanks

[Ying]

Thank you for sharing 🙂

[Steve]

This issue recently came up for me when working with Elements. I think it has to do with Cloudflare Managed WAF rules, perhaps not recognizing those json requests as typical wordpress requests. Super useful solution shared by Tom!

[IAN]

I’m having the same problem today. I used WP Reset to delete everything last night due to getting this message. Started fresh this morning and I’m still getting this same “JSON” response now.

EDIT: Sounds like it’s not just a Generatepress problem, right?

Please can you explain how and where do I fix/allow this path?

[David]

Hi there,

there are many reasons why this can happen.
First place to start is – go to Settings > Permalinks, set the structure to default and click Save Change.
Then try editing and saving a post.

If the issues persists repeat his without any CDN or caches enabled.

And if its still an issue then check the Tools > Site Health and make sure there are no errors being reported.

When testing do it with a blank post and only use core blocks with any plugins except GPP disabled.

[Kip]

Ok I believe I have this “fixed.” I have created a Cloudflare rule to bypass uri paths containing /wp-json/v2/gp_elements/ and chose all the features (I don’t know which one of these actually allows the editing):
User Agent Blocking
Browser Integrity Check
Hotlink Protection
Security Level
Rate Limiting
Zone Lockdown
WAF Managed Rules
I do not understand why these calls are running through Cloudflare to begin with, but that’s why I’m using GP in the first place, to reduce the amount of code and fixes I need to make. Oh well.

[Author]

Posts