NO BUG: Can't save with code block (new or existing)

Bugs
1

Video: Bricks Save Issue - TechSmith Screencast

I have a strange issue that is happening on my production server (I can’t repro this locally). See the video above, which is as dumbed down / simplified as I can make it.

  1. Blank page, in Bricks
  2. Add a text block. Can save without any issues.
  3. Add a default code block, just with HTML (without even enabling execution). I receive a 403 when I save.

In short, I can’t save any page with a code block. I have many pages with code blocks and continue to work just fine. But I can’t make any changes or add new code blocks.

I have tried enabling / disabling code execution at the code block level, with no luck.

Also, “Enable code execution” is enabled at the site level (Bricks settings) and has been forever. I don’t have the option to resign all code blocks (from settings)…because I can’t save the page :frowning:

I am guessing this is some sort of permissions issue. Any ideas on how I can troubleshoot this?

2

Hi @MarkW,

if you inspect the save request with developer tools (network tab), what is the response. It might give you some clue.
Other than that, you can try to disable all plugins (especially performance and security ones), and check if that’s causing it.
Then, you may need to also check for any possible security thing on the server itself.

But like I said, first check the network response, as it might give some clues.

Let us know.
Matej

3

Thank you the response. Good news and bad news…

The good news is that the issue is now “resolved”, at least the extent I can save now. With supports help we eventually honed in on Cloudflare and, specifically, the Page Shield feature. I disabled that and the problem went away.

The bad news is that I still don’t know why this happened.

  • I re-enabled Page Shield and can still save
  • I have always had Page Shield enabled and, until recently, had no issues.
  • Bricks has no reports of Page Shield being a problem.

So, yes, I am able to save again which is great (and with Page Shield enabled) but no clue why this happened.

4

Hi @MarkW,

thank you so much for your response. Honestly, I don’t know - like you said, there are no reports (that I’m aware of) of Page Shield feature being incompatible, and I’m also not sure why this could happen. And to be honest, I’m not sure how the Page Shield feature exactly works and how it checks the requests.
It might be, that something was cached or something else “restarted” when you toggled that feature. No idea, just a guess.

If this happens again, please keep us updated.

Thanks,
Matej

1 Like