Row Layout causing server error (500/508)

Hey,
Thanks for posting.

Hmm, that is odd.

Can you send me an export of the page so I can try to see what is happening?

What version of Gutenberg are you using?

Are you manually editing anything in the code editor? Are you using any plugins that extend all blocks?

Thanks,

Ben

Thanks, I have found a solution but it doesn’t shed any light on what went wrong. I created a fresh page and copy/pasted the content over. The copy of the page is now set as my home page and is working flawlessly – no server spikes – so I don’t know why the old one was causing problems. (I still have the dodgy page if you want an export of it).

In case it is helpful to you:

I was using Gutenberg 1.4.0;

I also had Atomic blocks active, and in an earlier draft of the page in question had both Atomic and Kadence blocks content active on the same page and working happily. However there are two reasons that I don’t think it was Atomic blocks because:

(1) When the problem started I think I had deleted the atomic blocks content so there should have been no scripts activated by the page – although Atomic blocks was still active within Gutenberg.

(2) To try and troubleshoot I deactivated both Atomic blocks and Kadence (along with several other plugins), at which point the stopped causing problems. Reactivating just the Kadence row block (which was the main one I was using) started up the problems again (Atomic blocks remained inactive). I intend to try reactivating Atomic blocks and inserting some content on the page to see if the same problem occurs – if it does I will let you know.

In case it is relevant: the problem initially showed up when trying to view an autosave of the page (because Gutenberg saves so often I had 42 autosaves!). To begin with, the error only showed up when trying to view the autosave, but after a couple of times of getting my server permissions reset just attempting to edit the page did it. I thought there might be a problem in the autosave file becoming corrupted, so I deleted all of my autosaves but the problem still persisted.

– – –

Custom CSS in use:

.image-shadow img {
box-shadow: 0 3px 10px rgba(0, 0, 0, 0.4);
}
.fetched {
box-shadow: 0 3px 10px rgba(0, 0, 0, 0.4);
border-radius: 1%;
border: 1px solid #333333;;
}
.feedzy-rss .rss_item {
border-bottom: none;
}
body a {
text-decoration: none !important;
}

I don’t believe there would be any issue running Atomic blocks.

Interesting that it started when you were looking at autosaves,

How were you adding the ‘image-shaddow’ class?

If you could send me a copy of the page I would be happy to take a look. I’m not sure how else I would be able to recreate.

Ben