SOLVED: JSON issue on page (page not saving, then 503 error)

Bugs
1

Issue: page not saving, followed by 503 error.

My hosting company just informed me of the following:
"There is something corrupt within the home page where Bricks hangs and causes a PHP timeout, we tested with allocating more resources but this makes no difference.

When we remove the Brick page JSON data from the _bricks_page_content_2 metakey of page ID 106 (home page) from the postmeta table of the database, the page does load (but without your page data of course).

The wisest thing is to report this problem to Bricks and share our findings with them, perhaps they have seen this before or this is a bug. Alternatively, we could delete the page data, but then you would have to rebuild the page with the risk of this problem returning."

I have just contacted Bricks support. I have reported this also on Bricks Facebook and here, just to let other people know that this issue can happen. Hope a solution will be found soon.

Lydia

2

UPDATE: issue was solved. Bricks Support has removed the code that led to Bricks ‘hanging’ and a PHP time out.

I was just editing in Bricks. No use of templates, no use of third party plugins. And that was sufficient to cause this issue.

I am now going to make a backup every hour of work that is done, so I can easily revert back. But I hope further issues will not occur.

3

The reason for the problem was a corrupted heading element, which was fixed by one of our developers.

Looking back, it’s impossible to say exactly what caused the problem, but yes, backups are always a good idea.

Glad we could help,
have a great weekend!

1 Like
4

I did have a weird issue when I experimented with shape dividers in sections. These were very enlarged, to play with the layout.

But it had an unwanted side effect: the header on the mobile version went really wide. Like 10 times the width of the mobile, and created a vertical scroling effect.

Only the logo could be seen on the front end. After some vertical scrolling the hamburger, and after more vertical scrolling the language switcher.

After the bad code was removed by Bricks, I removed all the elements from the page.

But that effect was still there, and can’t be right. Like some bad code was still lingering.

It was solved by putting a new section on the page, though.

Also, I was working really fast, so I also had the idea that when you change elements too fast, maybe the builder can’t keep up and starts writing bad code.

It is a pity that the cause can’t be found, but hopefully new issues won’t arise. Otherwise I will just leave this site in Elementor :grinning: